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

["Ross Philipson" <Ross.Philipson@xxxxxxxxxx>]

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.

Thanks
Ross

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

Ross Philipson schrieb:
> You will have to build it and then run the dump tool. If you use the all
> option it will dump everything. I then have a little tool that prints
> out the DMAR in human readable form so we can see what the DRHD
> reporting structures look like. 

Here we go:

www.plzk.de/acpidump.txt

-- 
stefan.bauer@xxxxxxxxxxx                Cubewerk
Tel   +49 8621 996 02 37                IT-Beratung + Planung
Tel   +49  179 119 47 67                Verkauf von Hard und Software
Fax   +49 1212 511057903                Herzog-Otto-Straße 32
http://www.cubewerk.de                  83308 Trostberg

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

DMAR.txt
Description: DMAR.txt

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