WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue

To: "Stefan Bauer" <stefan.bauer@xxxxxxxxxxx>
Subject: RE: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue
From: "Ross Philipson" <Ross.Philipson@xxxxxxxxxx>
Date: Fri, 31 Oct 2008 13:08:15 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 31 Oct 2008 10:08:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <490B304D.7060000@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <49089D18.4030405@xxxxxxxxxxx><4908B669.7080108@xxxxxxxxxxx><409D32C55C48D34DB5E31C8AB29EB15B071C6E74@xxxxxxxxxxxxxxxxxxxxxx> <4908BC3C.3070307@xxxxxxxxxxx> <409D32C55C48D34DB5E31C8AB29EB15B071C6EA7@xxxxxxxxxxxxxxxxxxxxxx> <4908C6FC.9030307@xxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C018686CF47@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49096151.8090500@xxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C018686D126@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49098860.9050309@xxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C018686D17B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4909C811.9070105@xxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C018686D23C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><490AB8FC.1020807@xxxxxxxxxxx><715D42877B251141A38726ABF5CABF2C018686D43D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><490B16E4.2060604@xxxxxxxxxxx><409D32C55C48D34DB5E31C8AB29EB15B071C7730@xxxxxxxxxxxxxxxxxxxxxx><490B23AC.8020700@xxxxxxxxxxx><409D32C55C48D34DB5E31C8AB29EB15B071C777F@xxxxxxxxxxxxxxxxxxxxxx> <490B304D.7060000@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack7dKHkbRba7FXFTvSRhYMKWu+GewABoHIQ
Thread-topic: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue
Did you mention in an earlier email that you have the latest BIOS for
this system?

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefan Bauer
Sent: Friday, October 31, 2008 12:20 PM
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35
-VT-DIssue

Ross Philipson schrieb:
> Attached is a printout of your DMAR tables. Focusing on the following
failures that occurred later in the boot process:
> 
> (XEN) domain_context_mapping: can't find drhd for device (bus=0 dev=1f
func=2)
> (XEN) [VT-D]iommu.c:1545:d0 intel_iommu_add_device: context mapping
failed
> (XEN) domain_context_mapping: can't find drhd for device (bus=0 dev=1f
func=5)
> (XEN) [VT-D]iommu.c:1545:d0 intel_iommu_add_device: context mapping
failed
> 
> The DMAR only has two DRHD with 1 and 3 scope entries respectively for
device endpoints (covering devices 00:1b.0, 00:03.0, 00:03.2, 00:03.3).
There are no scope entries for entire bridges and there is not an
INCLUDE_ALL DRHD. This is what is causing the failure - no match. It
seems odd to me that there are so few entries.

Is there anything i can do to work on that problem further?

Regards

-- 
Stefan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>