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

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

Stefan,

So those errors happened during booting DOM0 and then you checked xm
dmesg, correct? Then you started a 2k VM and the system reset. Can you
rebuild xen with debug=y, you might get more information about why the
context mapping is failing. We could also put some more trace in there
to see exactly what happens. 

Can you attach a serial cable and send the output from xen and dom0 to
COM1 or something like that? There may be some relevant information
traced out right before the reset that you are not seeing (it is
probably a crash in xen that is resetting the system).

Ross

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefan Bauer
Sent: Wednesday, October 29, 2008 1:28 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] iommu: mapping reserved region failed - Q35 - VT-D
Issue

Xen 3.4 xen-unstable.hg from yesterday with debian etch on 64bit arch
Intel/Lenovo Q35 Mainboard with VT-d enabled

Bootoptions iommu=1 vtd=1
pci.backhide for a PCI-E nvidia graphiccard

xm dmesg Error messages includes:

[VT-D] iommu.c: 1694:d32767 iommu: mapping reserved region failed
[VT-D] iommu.c: 1542:d0 intel_iommu_add_device: context mapping failed

If i try to start my HVM by xm create win2k the system reboots

any ideas?

-- 
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