iommu: mapping reserved region failed - Q35 - VT-D Issue

iommu: mapping reserved region failed - Q35 - VT-D Issue

[Stefan Bauer]

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

Re: iommu: mapping reserved region failed - Q35 - VT-D Issue

[Stefan Bauer]

Stefan Bauer schrieb:
> Bootoptions iommu=1 vtd=1
> pci.backhide for a PCI-E nvidia graphiccard

As mentioned in Documentation/Intel-IOMMU.txt boot option

intel_iommu=igfx_off did not change anything.

Regards

-- 
stefan.bauer@cubewerk.de		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

RE: iommu: mapping reserved region failed - Q35 - VT-D Issue

[Ross Philipson]

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@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Wednesday, October 29, 2008 1:28 PM
To: xen-devel@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: iommu: mapping reserved region failed - Q35 - VT-D Issue

[Stefan Bauer]

Ross Philipson schrieb:
> 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. 

I only found PCI Backend Debugging in the Xen menue which i
activacted, rebuild kernel and did again xm dmesg without further
informations. Do i have to activate it additionally?

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

I'll try it if my laptop becomes available (women...)

-- 

Stefan

RE: iommu: mapping reserved region failed - Q35 - VT-DIssue

[Ross Philipson]

I meant rebuild xen with debug=y. There is a bunch of tracing in the
routines that are trying to setup the context mapping that indicate what
is going on including tracing out what device it was dealing with when
things failed. Also (as mentioned in another email just sent), we can
enhance that logging in these routines to see if the hardware remapping
unit is missing for this device or something related.

Also again I was curious - it seems the failure trace you reported below
was during dom0 boot - is this true?

Thanks
Ross

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Wednesday, October 29, 2008 3:16 PM
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35 -
VT-DIssue

Ross Philipson schrieb:
> 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. 

I only found PCI Backend Debugging in the Xen menue which i
activacted, rebuild kernel and did again xm dmesg without further
informations. Do i have to activate it additionally?

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

I'll try it if my laptop becomes available (women...)

-- 

Stefan


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

Re: iommu: mapping reserved region failed - Q35 - VT-DIssue

[Stefan Bauer]

Ross Philipson schrieb:
> I meant rebuild xen with debug=y. There is a bunch of tracing in the
> routines that are trying to setup the context mapping that indicate what
> is going on including tracing out what device it was dealing with when
> things failed. Also (as mentioned in another email just sent), we can
> enhance that logging in these routines to see if the hardware remapping
> unit is missing for this device or something related.

debug=y can just be applied right after make linux-2.6-xen-build? or
where do i supply that debug=y ?

> Also again I was curious - it seems the failure trace you reported below
> was during dom0 boot - is this true?

Yes it's all during dom0 booting.

-- 
Stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Ross Philipson]

For rebuilding the xen part - the messages are coming out of the
hypervisor. E.g:

xen-unstable.hg/xen/make install debug=y

Ross

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Wednesday, October 29, 2008 3:41 PM
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35
-VT-DIssue

Ross Philipson schrieb:
> I meant rebuild xen with debug=y. There is a bunch of tracing in the
> routines that are trying to setup the context mapping that indicate
what
> is going on including tracing out what device it was dealing with when
> things failed. Also (as mentioned in another email just sent), we can
> enhance that logging in these routines to see if the hardware
remapping
> unit is missing for this device or something related.

debug=y can just be applied right after make linux-2.6-xen-build? or
where do i supply that debug=y ?

> Also again I was curious - it seems the failure trace you reported
below
> was during dom0 boot - is this true?

Yes it's all during dom0 booting.

-- 
Stefan

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

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

[-- Attachment #1: Type: text/plain, Size: 214 bytes --]

Ross Philipson schrieb:
> For rebuilding the xen part - the messages are coming out of the
> hypervisor. E.g:
> 
> xen-unstable.hg/xen/make install debug=y

Done, xenddebug.log attached.

HTH

Regards

-- 
Stefan


[-- Attachment #2: xenddebug.log --]
[-- Type: text/plain, Size: 20183 bytes --]

[2008-10-29 22:04:37 2430] INFO (__init__:1072) Xend Daemon started
[2008-10-29 22:04:37 2430] INFO (__init__:1072) Xend changeset: Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb.
[2008-10-29 22:04:37 2430] DEBUG (__init__:1072) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5073756273L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 524288L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
[2008-10-29 22:04:37 2430] INFO (__init__:1072) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2008-10-29 22:04:37 2430] DEBUG (__init__:1072) Adding Domain: 0
[2008-10-29 22:04:37 2430] DEBUG (__init__:1072) number of vcpus to use is 0
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VBD.set_device not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VBD.set_type not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: session.get_all_records not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: event.get_record not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: event.get_all not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VM.get_auto_power_on not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VM.set_auto_power_on not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VIF.get_network not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VIF.set_device not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VIF.set_MAC not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: VIF.set_MTU not found
[2008-10-29 22:04:37 2430] WARNING (__init__:1072) API call: debug.get_all not found
[2008-10-29 22:04:37 2430] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server.
[2008-10-29 22:04:37 2430] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.
[2008-10-29 22:04:37 2430] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch
[2008-10-29 22:14:59 2185] INFO (__init__:1072) Xend Daemon started
[2008-10-29 22:14:59 2185] INFO (__init__:1072) Xend changeset: Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb.
[2008-10-29 22:14:59 2185] DEBUG (__init__:1072) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 6287221482L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 524288L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
[2008-10-29 22:14:59 2185] INFO (__init__:1072) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2008-10-29 22:14:59 2185] DEBUG (__init__:1072) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'}
[2008-10-29 22:14:59 2185] DEBUG (__init__:1072) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '524288', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1', 'console/type': 'xenconsoled'}
[2008-10-29 22:14:59 2185] DEBUG (__init__:1072) Adding Domain: 0
[2008-10-29 22:14:59 2185] DEBUG (__init__:1072) number of vcpus to use is 0
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VBD.set_device not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VBD.set_type not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: session.get_all_records not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: event.get_record not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: event.get_all not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VM.get_auto_power_on not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VM.set_auto_power_on not found
[2008-10-29 22:14:59 2185] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VIF.get_network not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VIF.set_device not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VIF.set_MAC not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: VIF.set_MTU not found
[2008-10-29 22:14:59 2185] WARNING (__init__:1072) API call: debug.get_all not found
[2008-10-29 22:14:59 2185] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server.
[2008-10-29 22:14:59 2185] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.
[2008-10-29 22:16:33 2185] DEBUG (__init__:1072) SrvServer.cleanup()
[2008-10-29 22:16:33 2185] DEBUG (__init__:1072) XMLRPCServer.cleanup()
[2008-10-29 22:16:33 2185] DEBUG (__init__:1072) XMLRPCServer.cleanup()
[2008-10-29 22:16:33 2185] DEBUG (__init__:1072) cleanup_domains
[2008-10-29 22:16:33 2383] INFO (__init__:1072) Xend Daemon started
[2008-10-29 22:16:33 2180] INFO (__init__:1072) Xend exited with status 0.
[2008-10-29 22:16:33 2383] INFO (__init__:1072) Xend changeset: Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb.
[2008-10-29 22:16:33 2383] DEBUG (__init__:1072) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 7764192080L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 524288L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
[2008-10-29 22:16:33 2383] INFO (__init__:1072) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2008-10-29 22:16:33 2383] DEBUG (__init__:1072) Adding Domain: 0
[2008-10-29 22:16:33 2383] DEBUG (__init__:1072) number of vcpus to use is 0
[2008-10-29 22:16:33 2383] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VBD.set_device not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VBD.set_type not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: session.get_all_records not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: event.get_record not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: event.get_all not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VM.get_auto_power_on not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VM.set_auto_power_on not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VIF.get_network not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VIF.set_device not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VIF.set_MAC not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: VIF.set_MTU not found
[2008-10-29 22:16:33 2383] WARNING (__init__:1072) API call: debug.get_all not found
[2008-10-29 22:16:33 2383] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server.
[2008-10-29 22:16:33 2383] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) XendDomainInfo.create(['vm', ['name', 'win2k'], ['memory', 512], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['vcpus', 1], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['boot', 'c'], ['fda', ''], ['fdb', ''], ['timer_mode', 1], ['localtime', 0], ['serial', ''], ['stdvga', 0], ['isa', 0], ['nographic', 0], ['soundhw', ''], ['vnc', 0], ['vncunused', 1], ['xauthority', '/root/.Xauthority'], ['rtc_timeoffset', '0'], ['monitor', 0], ['acpi', 0], ['apic', 1], ['usb', 1], ['usbdevice', 'tablet'], ['keymap', ''], ['pci', [['0x0', '0x01', '0x00', '0x0']]], ['hpet', 0], ['guest_os_type', 'default'], ['hap', 1], ['cpuid', []], ['cpuid_check', []], ['viridian', 0]]], ['device', ['vbd', ['uname', 'file:/xen/win2k-32.img'], ['dev', 'ioemu:hda'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:/dev/cdrom'], ['dev', 'hdc:cdrom'], ['mode', 'r']]], ['device', ['pci', ['dev', ['domain', '0x0'], ['bus', '0x01'], ['slot', '0x00'], ['func', '0x0']]]], ['device', ['vif', ['mac', '00:16:3E:00:00:04'], ['type', 'ioemu']]]])
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) XendDomainInfo.constructDomain
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) Balloon: 2539328 KiB free; need 2048; done.
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) Adding Domain: 1
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) XendDomainInfo.initDomain: 1 256
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: boot, val: c
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: fda, val: None
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: fdb, val: None
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: soundhw, val: None
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: localtime, val: 0
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: serial, val: None
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: std-vga, val: 0
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: isa, val: 0
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: acpi, val: 0
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: usb, val: 1
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) args: usbdevice, val: tablet
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) _initDomain:shadow_memory=0x0, memory_static_max=0x20000000, memory_static_min=0x0.
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) Balloon: 2538036 KiB free; need 539648; done.
[2008-10-29 22:17:01 2383] INFO (__init__:1072) buildDomain os=hvm dom=1 vcpus=1
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) domid          = 1
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) image          = /usr/lib/xen/boot/hvmloader
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) store_evtchn   = 2
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) memsize        = 512
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) vcpus          = 1
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) acpi           = 0
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) apic           = 1
[2008-10-29 22:17:01 2383] INFO (__init__:1072) createDevice: vbd : {'uuid': 'f7b3f2d9-2c9f-5c32-09fd-de80d0cc93b0', 'bootable': 1, 'driver': 'ioemu', 'dev': 'ioemu:hda', 'uname': 'file:/xen/win2k-32.img', 'mode': 'w'}
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/768'} to /local/domain/1/device/vbd/768.
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) DevController: writing {'domain': 'win2k', 'frontend': '/local/domain/1/device/vbd/768', 'uuid': 'f7b3f2d9-2c9f-5c32-09fd-de80d0cc93b0', 'dev': 'hda', 'state': '1', 'params': '/xen/win2k-32.img', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/768.
[2008-10-29 22:17:01 2383] INFO (__init__:1072) createDevice: vbd : {'uuid': '44295b8b-d662-da0b-c642-9e6c8c0880da', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'uname': 'phy:/dev/cdrom', 'mode': 'r'}
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) DevController: writing {'backend-id': '0', 'virtual-device': '5632', 'device-type': 'cdrom', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/5632'} to /local/domain/1/device/vbd/5632.
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) DevController: writing {'domain': 'win2k', 'frontend': '/local/domain/1/device/vbd/5632', 'uuid': '44295b8b-d662-da0b-c642-9e6c8c0880da', 'dev': 'hdc', 'state': '1', 'params': '/dev/cdrom', 'mode': 'r', 'online': '1', 'frontend-id': '1', 'type': 'phy'} to /local/domain/0/backend/vbd/1/5632.
[2008-10-29 22:17:01 2383] INFO (__init__:1072) createDevice: vif : {'mac': '00:16:3E:00:00:04', 'type': 'ioemu', 'uuid': '649b3f76-9e6d-0a39-b5c4-ca83bfb09959'}
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0.
[2008-10-29 22:17:01 2383] DEBUG (__init__:1072) DevController: writing {'domain': 'win2k', 'frontend': '/local/domain/1/device/vif/0', 'uuid': '649b3f76-9e6d-0a39-b5c4-ca83bfb09959', 'script': '/etc/xen/scripts/vif-bridge', 'mac': '00:16:3E:00:00:04', 'frontend-id': '1', 'state': '1', 'online': '1', 'handle': '0', 'type': 'ioemu'} to /local/domain/0/backend/vif/1/0.
[2008-10-29 22:17:01 2383] INFO (__init__:1072) createDevice: pci : {'devs': [{'slot': '0x00', 'bus': '0x01', 'domain': '0x0', 'uuid': '8a4e3fdb-df1e-3ad0-b405-fb1db0b842e3', 'func': '0x0'}], 'uuid': '28309778-d69d-c23b-84ab-c1abf724423b'}
[2008-10-29 22:17:41 2198] INFO (__init__:1072) Xend Daemon started
[2008-10-29 22:17:41 2198] INFO (__init__:1072) Xend changeset: Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb.
[2008-10-29 22:17:42 2198] DEBUG (__init__:1072) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 3542792679L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 524288L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
[2008-10-29 22:17:42 2198] INFO (__init__:1072) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2008-10-29 22:17:42 2198] DEBUG (__init__:1072) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'}
[2008-10-29 22:17:42 2198] DEBUG (__init__:1072) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '524288', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1', 'console/type': 'xenconsoled'}
[2008-10-29 22:17:42 2198] DEBUG (__init__:1072) Adding Domain: 0
[2008-10-29 22:17:42 2198] DEBUG (__init__:1072) number of vcpus to use is 0
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VBD.set_device not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VBD.set_type not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: session.get_all_records not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: event.get_record not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: event.get_all not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VM.get_auto_power_on not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VM.set_auto_power_on not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VIF.get_network not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VIF.set_device not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VIF.set_MAC not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: VIF.set_MTU not found
[2008-10-29 22:17:42 2198] WARNING (__init__:1072) API call: debug.get_all not found
[2008-10-29 22:17:42 2198] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.
[2008-10-29 22:17:42 2198] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server.
[2008-10-29 22:17:42 2198] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch
[2008-10-29 22:20:06 2191] INFO (__init__:1072) Xend Daemon started
[2008-10-29 22:20:06 2191] INFO (__init__:1072) Xend changeset: Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb.
[2008-10-29 22:20:07 2191] DEBUG (__init__:1072) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 3537741542L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 524288L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
[2008-10-29 22:20:07 2191] INFO (__init__:1072) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2008-10-29 22:20:07 2191] DEBUG (__init__:1072) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'}
[2008-10-29 22:20:07 2191] DEBUG (__init__:1072) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '524288', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1', 'console/type': 'xenconsoled'}
[2008-10-29 22:20:07 2191] DEBUG (__init__:1072) Adding Domain: 0
[2008-10-29 22:20:07 2191] DEBUG (__init__:1072) number of vcpus to use is 0
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VBD.set_device not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VBD.set_type not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: session.get_all_records not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: event.get_record not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: event.get_all not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VM.get_auto_power_on not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VM.set_auto_power_on not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VIF.get_network not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VIF.set_device not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VIF.set_MAC not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: VIF.set_MTU not found
[2008-10-29 22:20:07 2191] WARNING (__init__:1072) API call: debug.get_all not found
[2008-10-29 22:20:07 2191] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server.
[2008-10-29 22:20:07 2191] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch
[2008-10-29 22:20:07 2191] INFO (__init__:1072) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock.
[2008-10-29 22:21:13 2191] DEBUG (__init__:1072) SrvServer.cleanup()
[2008-10-29 22:21:13 2191] DEBUG (__init__:1072) XMLRPCServer.cleanup()
[2008-10-29 22:21:13 2191] DEBUG (__init__:1072) XMLRPCServer.cleanup()
[2008-10-29 22:21:13 2191] DEBUG (__init__:1072) cleanup_domains
[2008-10-29 22:21:13 2186] INFO (__init__:1072) Xend exited with status 0.

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Han, Weidong]

Stefan Bauer wrote:
> Ross Philipson schrieb:
>> For rebuilding the xen part - the messages are coming out of the
>> hypervisor. E.g: 
>> 
>> xen-unstable.hg/xen/make install debug=y
> 
> Done, xenddebug.log attached.
> 
> HTH
> 
> Regards

Stefan,

xenddebug.log is not helpful. when you compile xen, pls use: make xen debug=y

or add "loglvl=all loglvl_guest=all" in grub kernel line like:
	kernel /boot/xen.gz dom0_mem=512m iommu=1 loglvl=all loglvl_guest=all

Per xm-dmesg in your another mail, I am very curious on why domain_context_mapping failed (which also result in failure of reserved memory mapping). 

Per dom0 failure info (pci_bus_probe_wapper()), which is caused by pci_remove_device(), I suspect the devices are not added to alldevs_list.

Pls use above method to catch more debug info, then we can analyse the info easily.

Regards,
Weidong

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

[-- Attachment #1: Type: text/plain, Size: 385 bytes --]

Han, Weidong schrieb:
> or add "loglvl=all loglvl_guest=all" in grub kernel line like:
> 	kernel /boot/xen.gz dom0_mem=512m iommu=1 loglvl=all loglvl_guest=all

Weidong,

please see attached a even more verbose debugging output.
Unfortunatel i was not able to redirect the console output to a serial
terminal, so i took a screenshot[1].

[1] www.plzk.de/IMG_2598.JPG

HTH

-- 
Stefan


[-- Attachment #2: xen-dmesg --]
[-- Type: text/plain, Size: 17076 bytes --]

Bootdata ok (command line is root=/dev/sda2 ro pciback.hide=(01:00.0))
Linux version 2.6.18.8-xen (root@xen64) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #2 SMP Wed Oct 29 20:59:53 CET 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000020800000 (usable)
DMI present.
On node 0 totalpages: 128565
  DMA zone: 1305 pages, LIFO batch:0
  DMA32 zone: 127260 pages, LIFO batch:31
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: LENOVO   Product ID: THINKCEN APIC at: 0xFEE00000
I/O APIC #2 Version 32 at 0xFEC00000.
Setting APIC routing to xen
Processors: 2
Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
Built 1 zonelists.  Total pages: 128565
Kernel command line: root=/dev/sda2 ro pciback.hide=(01:00.0)
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2327.510 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB enabled: 
 Aperture:     64 megabytes
 Kernel range: ffff8800018fd000 - ffff8800058fd000
 Address size: 27 bits
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Memory: 438812k/532480k available (1699k kernel code, 85336k reserved, 734k data, 136k init)
Calibrating delay using timer specific routine.. 4657.02 BogoMIPS (lpj=23285122)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Freeing SMP alternatives: 24k freed
GSI 16 sharing vector 0xA8 and IRQ 16
GSI 17 sharing vector 0xB0 and IRQ 17
GSI 18 sharing vector 0xB8 and IRQ 18
GSI 19 sharing vector 0xC0 and IRQ 19
GSI 20 sharing vector 0xC8 and IRQ 20
Brought up 2 CPUs
Initializing CPU#1
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
migration_cost=12
Unpacking initramfs... done
Freeing initrd memory: 5539k freed
PM: Adding info for No Bus:platform
NET: Registered protocol family 16
PM: Adding info for No Bus:xen
PM: Adding info for No Bus:xen-backend
PCI: Using configuration type 1
xen_mem: Initialising balloon driver.
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PM: Adding info for No Bus:pci0000:00
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.2
Boot video device is 0000:11:0c.0
PCI: Transparent bridge - 0000:00:1e.0
PM: Adding info for pci:0000:00:00.0
PM: Adding info for pci:0000:00:01.0
PM: Adding info for pci:0000:00:03.0
PM: Adding info for pci:0000:00:03.2
PM: Adding info for pci:0000:00:03.3
PM: Adding info for pci:0000:00:19.0
PM: Adding info for pci:0000:00:1a.0
PM: Adding info for pci:0000:00:1a.1
PM: Adding info for pci:0000:00:1a.2
PM: Adding info for pci:0000:00:1a.7
PM: Adding info for pci:0000:00:1b.0
PM: Adding info for pci:0000:00:1d.0
PM: Adding info for pci:0000:00:1d.1
PM: Adding info for pci:0000:00:1d.2
PM: Adding info for pci:0000:00:1d.7
PM: Adding info for pci:0000:00:1e.0
PM: Adding info for pci:0000:00:1f.0
PM: Adding info for pci:0000:00:1f.2
PM: Adding info for pci:0000:00:1f.3
PM: Adding info for pci:0000:00:1f.5
PM: Adding info for pci:0000:01:00.0
PM: Adding info for pci:0000:11:0c.0
PCI->APIC IRQ transform: 0000:00:01.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:03.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:03.2[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:03.3[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:19.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1a.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1a.1[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1a.2[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:1a.7[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:1b.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1d.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1d.1[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1d.2[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:1d.7[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1f.2[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1f.3[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1f.5[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:01:00.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:11:0c.0[A] -> IRQ 20
pciback: wants to seize 0000:01:00.0
pciback 0000:00:00.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:01.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:03.0: probing...
pciback 0000:00:03.2: probing...
pciback 0000:00:03.3: probing...
pciback 0000:00:19.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1a.0: probing...
pciback 0000:00:1a.1: probing...
pciback 0000:00:1a.2: probing...
pciback 0000:00:1a.7: probing...
pciback 0000:00:1b.0: probing...
pciback 0000:00:1d.0: probing...
pciback 0000:00:1d.1: probing...
pciback 0000:00:1d.2: probing...
pciback 0000:00:1d.7: probing...
pciback 0000:00:1e.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.2: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.3: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.5: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:01:00.0: probing...
pciback 0000:01:00.0: seizing device
pciback 0000:01:00.0: pcistub_device_alloc
pciback 0000:01:00.0: deferring initialization
pciback 0000:11:0c.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

PCI: Failed to allocate mem resource #6:20000@d0000000 for 0000:01:00.0
PCI: Bridge: 0000:00:01.0
  IO window: 2000-2fff
  MEM window: d0000000-d2ffffff
  PREFETCH window: c0000000-cfffffff
PCI: Bridge: 0000:00:1e.0
  IO window: disabled.
  MEM window: d4000000-d5ffffff
  PREFETCH window: d3000000-d30fffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 5, 131072 bytes)
TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 65536 bind 32768)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1225353980.574:1): initialized
audit: cannot initialize inotify handle
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
pciback: pcistub_init_devices_late
pciback 0000:01:00.0: initializing...
pciback 0000:01:00.0: initializing config
pciback 0000:01:00.0: initializing virtual configuration space
pciback 0000:01:00.0: added config field at offset 0x04
pciback 0000:01:00.0: added config field at offset 0x3c
pciback 0000:01:00.0: added config field at offset 0x3d
pciback 0000:01:00.0: added config field at offset 0x0c
pciback 0000:01:00.0: added config field at offset 0x0d
pciback 0000:01:00.0: added config field at offset 0x0f
pciback 0000:01:00.0: added config field at offset 0x10
pciback 0000:01:00.0: added config field at offset 0x14
pciback 0000:01:00.0: added config field at offset 0x18
pciback 0000:01:00.0: added config field at offset 0x1c
pciback 0000:01:00.0: added config field at offset 0x20
pciback 0000:01:00.0: added config field at offset 0x24
pciback 0000:01:00.0: added config field at offset 0x30
pciback 0000:01:00.0: Found capability 0x1 at 0x60
pciback 0000:01:00.0: added config field at offset 0x60
pciback 0000:01:00.0: added config field at offset 0x62
pciback 0000:01:00.0: added config field at offset 0x64
pciback 0000:01:00.0: added config field at offset 0x66
pciback 0000:01:00.0: added config field at offset 0x67
pciback 0000:01:00.0: enabling device
PCI: Enabling device 0000:01:00.0 (0104 -> 0107)
pciback 0000:01:00.0: reset device
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PM: Adding info for platform:i8042
serio: i8042 AUX port at 0x60,0x64 irq 12
PM: Adding info for serio:serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
PM: Adding info for serio:serio1
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 1
NET: Registered protocol family 17
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 136k freed
input: AT Translated Set 2 keyboard as /class/input/input0
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1C40 irq 14
scsi0 : ata_piix
PM: Adding info for No Bus:host0
ata1.00: ATA-7, max UDMA/133, 156312576 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
PM: Adding info for No Bus:target0:0:0
  Vendor: ATA       Model: WDC WD800JD-08MS  Rev: 10.0
  Type:   Direct-Access                      ANSI SCSI revision: 05
PM: Adding info for scsi:0:0:0:0
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1C48 irq 15
scsi1 : ata_piix
PM: Adding info for No Bus:host1
ata2.00: ATAPI, max UDMA/33
ata2.00: configured for UDMA/33
PM: Adding info for No Bus:target1:0:0
  Vendor: TSSTcorp  Model: DVD-ROM TS-H353B  Rev: LE06
  Type:   CD-ROM                             ANSI SCSI revision: 05
PM: Adding info for scsi:1:0:0:0
ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ]
PCI: Setting latency timer of device 0000:00:1f.5 to 64
ata3: SATA max UDMA/133 cmd 0x1CB8 ctl 0x1CAE bmdma 0x1C60 irq 18
ata4: SATA max UDMA/133 cmd 0x1CB0 ctl 0x1CAA bmdma 0x1C68 irq 18
scsi2 : ata_piix
PM: Adding info for No Bus:host2
ATA: abnormal status 0x7F on port 0x1CBF
scsi3 : ata_piix
PM: Adding info for No Bus:host3
ATA: abnormal status 0x7F on port 0x1CB7
SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: Attached scsi disk sda
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
sr0: scsi3-mmc drive: 47x/47x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 1:0:0:0: Attached scsi generic sg1 type 5
Adding 289160k swap on /dev/sda3.  Priority:-1 extents:1 across:289160k
EXT3 FS on sda2, internal journal
usbcore: registered new driver usbkbd
/usr/src/linux-2.6.18-xen.hg/drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.


[-- Attachment #3: xm-dmesg --]
[-- Type: text/plain, Size: 16385 bytes --]

[VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:644: iommu_enable_translation: iommu->reg = ffff828bfff58000
(XEN) [VT-D]iommu.c:644: iommu_enable_translation: iommu->reg = ffff828bfff57000
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x531ecc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   00000000b9000000->00000000ba000000 (126976 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff80531ecc
(XEN)  Init. ramdisk: ffffffff80532000->ffffffff80a9ac00
(XEN)  Phys-Mach map: ffffffff80a9b000->ffffffff80b9b000
(XEN)  Start info:    ffffffff80b9b000->ffffffff80b9b4a4
(XEN)  Page tables:   ffffffff80b9c000->ffffffff80ba7000
(XEN)  Boot stack:    ffffffff80ba7000->ffffffff80ba8000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: ........................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 108kB init memory.
(XEN) PCI add device 00:00.0
(XEN) PCI remove device 00:00.0
(XEN) PCI add device 00:01.0
(XEN) PCI remove device 00:01.0
(XEN) PCI add device 00:03.0
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) PCI remove device 00:03.0
(XEN) PCI add device 00:03.2
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) PCI remove device 00:03.2
(XEN) PCI add device 00:03.3
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) PCI remove device 00:03.3
(XEN) PCI add device 00:19.0
(XEN) PCI remove device 00:19.0
(XEN) PCI add device 00:1a.0
(XEN) PCI remove device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI remove device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI remove device 00:1a.2
(XEN) PCI add device 00:1a.7
(XEN) PCI remove device 00:1a.7
(XEN) PCI add device 00:1b.0
(XEN) PCI remove device 00:1b.0
(XEN) PCI add device 00:1d.0
(XEN) PCI remove device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI remove device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI remove device 00:1d.2
(XEN) PCI add device 00:1d.7
(XEN) PCI remove device 00:1d.7
(XEN) PCI add device 00:1e.0
(XEN) PCI remove device 00:1e.0
(XEN) PCI add device 00:1f.0
(XEN) PCI remove device 00:1f.0
(XEN) PCI add device 00:1f.2
(XEN) PCI remove device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI remove device 00:1f.3
(XEN) PCI add device 00:1f.5
(XEN) PCI remove device 00:1f.5
(XEN) PCI add device 01:00.0
(XEN) PCI add device 11:0c.0
(XEN) PCI remove device 11:0c.0
(XEN) PCI add device 00:03.2
(XEN) [VT-D]iommu.c:452: IOMMU: tlb flush request 2, actual 1
(XEN) PCI remove device 00:03.2
(XEN) [VT-D]iommu.c:1542:d0 intel_iommu_add_device: context mapping failed
(XEN) [VT-D]iommu.c:1542:d0 intel_iommu_add_device: context mapping failed
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.5


[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

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

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Stefan Bauer schrieb:
> [1] www.plzk.de/IMG_2598.JPG

File updated, i uploaded the wrong one, sorry for that.

-- 
Stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Han, Weidong]

Stefan Bauer wrote:
> Han, Weidong schrieb:
>> or add "loglvl=all loglvl_guest=all" in grub kernel line like:
>> 	kernel /boot/xen.gz dom0_mem=512m iommu=1 loglvl=all
>> loglvl_guest=all 
> 
> Weidong,
> 
> please see attached a even more verbose debugging output.
> Unfortunatel i was not able to redirect the console output to a serial
> terminal, so i took a screenshot[1].

Can you add some printk in domain_context_mapping()? Where does it exit?

You'd better make serial console work. Following is my grub including serial console config. 

title 3: xen on RHEL5 (x86_64)
        root (hd0,0)
        kernel /boot/xen.gz dom0_mem=512m console=com1 iommu=1 loglvl=all loglvl_guest=all
        module /boot/vmlinuz-2.6.18.8-xen ro root=/dev/sda1 xencons=ttyS console=tty0 console=ttyS0, pciback.hide=(01:00.0)
        module /boot/initrd-2.6.18.8-xen.img

Regards,
Weidong

> 
> [1] www.plzk.de/IMG_2598.JPG
> 
> HTH

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Han, Weidong schrieb:
> You'd better make serial console work. Following is my grub including serial console config. 

Weidong,

i get my hands on a usb-serial adapter, please see the output right here:

www.plzk.de/xendebug-serial.txt

Hope that helps.

Regards

-- 
Stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Han, Weidong]

Stefan Bauer wrote:
> Han, Weidong schrieb:
>> You'd better make serial console work. Following is my grub
>> including serial console config. 
> 
> Weidong,
> 
> i get my hands on a usb-serial adapter, please see the output right
> here: 
> 
> www.plzk.de/xendebug-serial.txt

Why it's so short? Can post complete output?

And also that is a panic. Why it's not consistent with the sighting described in your previous mails?

I suspect your environment is not incorrect in somewhere. Pls list the following info: platform, BIOS, dom0 changeset, Xen changeset, did you add-on extra graphics card? did you follow steps listed in docs/misc/vtd.txt?

Actually, latest Xen VT-d is quite stable in our recent testing.

Regards,
Weidong

> 
> Hope that helps.
> 
> Regards

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Han, Weidong schrieb:
> Why it's so short? Can post complete output?

I expected also an even bigger output, but it shows debug=n even
though i enabled it with loglvl=all loglvl_guest=all

Please see the new complete output here:

www.plzk.de/CAPTURE.TXT

> I suspect your environment is not incorrect in somewhere. Pls list the following info: platform, BIOS, dom0 changeset, Xen changeset, did you add-on extra graphics card? did you follow steps listed in docs/misc/vtd.txt?

64BIT Debian stable (etch)
Lenovo Thinkcentre M57 - Typ 6075-BQG
Bios Version 2RKT54AUS
Bios Date 08/20/2008
Dom0 is 2.6.18.8-xen Kernel with Xen 3.4 xen-unstable.hg, plain
installation without any modifications at all

One HVM guest for testing, windows 2000 with pci = [ ' 01:00.0' ] line
in its configuration.

I add a pci graphic card for testing purpose to have vga output in
case i hide the pci-e card. that pci card is not used for passthrough.

I followed steps listed in
http://lxr.xensource.com/lxr/source/docs/misc/vtd.txt but came to the
conclusion that it might have something to do with Base Address Register?


> Actually, latest Xen VT-d is quite stable in our recent testing.
I wish here too.

Regards

-- 
Stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Han, Weidong]

Stefan Bauer wrote:
> Han, Weidong schrieb:
>> Why it's so short? Can post complete output?
> 
> I expected also an even bigger output, but it shows debug=n even
> though i enabled it with loglvl=all loglvl_guest=all
> 
> Please see the new complete output here:
> 
> www.plzk.de/CAPTURE.TXT

Yes, this output is complete and helpful. I found the problem exists in domain_context_mapping(), which never succeeds. Thus result in other problems. Can you add some printk to locate where it fails?

In addition, I suggest you don't add extra graphic card into your machine, as I know it may introduce issues on Q35. 

Regards,
Weidong

> 
>> I suspect your environment is not incorrect in somewhere. Pls list
>> the following info: platform, BIOS, dom0 changeset, Xen changeset,
>> did you add-on extra graphics card? did you follow steps listed in
>> docs/misc/vtd.txt?   
> 
> 64BIT Debian stable (etch)
> Lenovo Thinkcentre M57 - Typ 6075-BQG
> Bios Version 2RKT54AUS
> Bios Date 08/20/2008
> Dom0 is 2.6.18.8-xen Kernel with Xen 3.4 xen-unstable.hg, plain
> installation without any modifications at all
> 
> One HVM guest for testing, windows 2000 with pci = [ ' 01:00.0' ] line
> in its configuration.
> 
> I add a pci graphic card for testing purpose to have vga output in
> case i hide the pci-e card. that pci card is not used for passthrough.
> 
> I followed steps listed in
> http://lxr.xensource.com/lxr/source/docs/misc/vtd.txt but came to the
> conclusion that it might have something to do with Base Address
> Register? 
> 
> 
>> Actually, latest Xen VT-d is quite stable in our recent testing. I
>> wish here too. 
> 
> Regards

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Han, Weidong schrieb:
> Yes, this output is complete and helpful. I found the problem exists in domain_context_mapping(), which never succeeds. Thus result in other problems. Can you add some printk to locate where it fails?

I will if you advice me how to do where exactly.

> In addition, I suggest you don't add extra graphic card into your machine, as I know it may introduce issues on Q35.  

Problem is that i want to use the pci-e card for my hvm guest and the
onboard one for dom0. it seems that both the onboard and pci-e one
cant work alongside, so iam forced to add another one.

Regards


-- 
Stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Ross Philipson]

Stefan,

Most of the paths through the function domain_context_mapping() (in
xen/drivers/passthrough/vtd/iommu.c) also trace extra information but I
don't see those traces so it is reasonable to assume that the function
is returning an error when the call to acpi_find_matched_drhd_unit()
fails to find a DRHD for the particular device. I would start by putting
a trace there in the failure case and trace out the bus/dev info
(presumably it is device 00:03.2). If this is the case then we can look
at your DMAR ACPI table - maybe this is a faulty BIOS issue (e.g. there
is no DRHD reporting INCLUDE_ALL devices).

Or I may be wrong and the logging level is just not set for those
gdprintk() calls in trace in the switch statement (though I don't think
this is the case). If it is the case put code after the various calls in
the switch statement to test the "ret" value and trace an error if it
fails.

Thanks
Ross


-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Friday, October 31, 2008 3:51 AM
Cc: 'xen-devel@lists.xensource.com'
Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35
-VT-DIssue

Han, Weidong schrieb:
> Yes, this output is complete and helpful. I found the problem exists
in domain_context_mapping(), which never succeeds. Thus result in other
problems. Can you add some printk to locate where it fails?

I will if you advice me how to do where exactly.

> In addition, I suggest you don't add extra graphic card into your
machine, as I know it may introduce issues on Q35.  

Problem is that i want to use the pci-e card for my hvm guest and the
onboard one for dom0. it seems that both the onboard and pci-e one
cant work alongside, so iam forced to add another one.

Regards


-- 
Stefan

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

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Ross Philipson schrieb:
> Stefan,
> 
> Most of the paths through the function domain_context_mapping() (in
> xen/drivers/passthrough/vtd/iommu.c) also trace extra information but I
> don't see those traces so it is reasonable to assume that the function
> is returning an error when the call to acpi_find_matched_drhd_unit()
> fails to find a DRHD for the particular device. I would start by putting
> a trace there in the failure case and trace out the bus/dev info
> (presumably it is device 00:03.2). If this is the case then we can look
> at your DMAR ACPI table - maybe this is a faulty BIOS issue (e.g. there
> is no DRHD reporting INCLUDE_ALL devices).

Sorry but thats a way to technically for me. I'm not familiar with C
nor any other higher programming language. I will provide informations
and do testing.

> Or I may be wrong and the logging level is just not set for those
> gdprintk() calls in trace in the switch statement (though I don't think
> this is the case). If it is the case put code after the various calls in
> the switch statement to test the "ret" value and trace an error if it

Regards

-- 
Stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Han, Weidong]

Stefan Bauer wrote:
> Han, Weidong schrieb:
>> Yes, this output is complete and helpful. I found the problem exists
>> in domain_context_mapping(), which never succeeds. Thus result in
>> other problems. Can you add some printk to locate where it fails?  
> 
> I will if you advice me how to do where exactly.

I think you can add printk after check of drhd:

     if ( !drhd )
+    {
+        printk("%s: can't find drhd for device (bus=%x dev=%x func=%x)\n",
+                __func__, bus, PCI_SLOT(devfn), PCI_FUNC(devfn));
         return -ENODEV;
+    }

and you also can change XENLOG_INFO to XENLOG_ERR in domain_context_mapping(). 

> 
>> In addition, I suggest you don't add extra graphic card into your
>> machine, as I know it may introduce issues on Q35. 
> 
> Problem is that i want to use the pci-e card for my hvm guest and the
> onboard one for dom0. it seems that both the onboard and pci-e one
> cant work alongside, so iam forced to add another one.
> 

A few months ago,  in xen mailing list I remember some guys reported: when using PEG card (turning off integrated Gfx) on Q35, VT-d cannot work. It's the bios issue. I suspect it's not fixed yet. So I suggest you to use IGD instead of PEG.

Regards,
Weidong

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Han, Weidong schrieb:
>      if ( !drhd )
> +    {
> +        printk("%s: can't find drhd for device (bus=%x dev=%x func=%x)\n",
> +                __func__, bus, PCI_SLOT(devfn), PCI_FUNC(devfn));
>          return -ENODEV;
> +    }
> 
> and you also can change XENLOG_INFO to XENLOG_ERR in domain_context_mapping(). 

Added and recompiled, output here:

www.plzk.de/CAPTURE2

> A few months ago,  in xen mailing list I remember some guys reported: when using PEG card (turning off integrated Gfx) on Q35, VT-d cannot work. It's the bios issue. I suspect it's not fixed yet. So I suggest you to use IGD instead of PEG.

I would, but if i do not select PEG in bios, lspci did not show the
PEG card.

Stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Ross Philipson]

OK, that is what I was going to give you anyway and that is sort of what
I expected. Can you get a dump of you ACPI DMAR table. You can use
pmtools to dump the ACPI tables:

http://kernel.org/pub/linux/kernel/people/lenb/acpi/utils/

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. 

Thanks
Ross

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Friday, October 31, 2008 10:32 AM
Cc: 'xen-devel@lists.xensource.com'
Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35
-VT-DIssue

Han, Weidong schrieb:
>      if ( !drhd )
> +    {
> +        printk("%s: can't find drhd for device (bus=%x dev=%x
func=%x)\n",
> +                __func__, bus, PCI_SLOT(devfn), PCI_FUNC(devfn));
>          return -ENODEV;
> +    }
> 
> and you also can change XENLOG_INFO to XENLOG_ERR in
domain_context_mapping(). 

Added and recompiled, output here:

www.plzk.de/CAPTURE2

> A few months ago,  in xen mailing list I remember some guys reported:
when using PEG card (turning off integrated Gfx) on Q35, VT-d cannot
work. It's the bios issue. I suspect it's not fixed yet. So I suggest
you to use IGD instead of PEG.

I would, but if i do not select PEG in bios, lspci did not show the
PEG card.

Stefan

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

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

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@cubewerk.de		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

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Ross Philipson]

[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]

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@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Friday, October 31, 2008 11:27 AM
Cc: xen-devel@lists.xensource.com
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@cubewerk.de		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@lists.xensource.com
http://lists.xensource.com/xen-devel

[-- Attachment #2: DMAR.txt --]
[-- Type: text/plain, Size: 4712 bytes --]

DMAR dump utility - input DMAR: DMAR.dat size: 200
DMA Remapping Reporting Structure
==================================================
Signature:        DMAR
Length:           0x000000c8
Revision:         0x01
Checksum:         0x9e
OEMID:            Intel 
OEM Table ID:     OEMDMAR 
OEM Revision:     0x060400d0
Creator ID:       LOHR
Creator Revision: 0x00000001
HAW:              0x23
Flags:            0x00
Reserved[10]: 00 00 00 00 00 00 00 00 00 00

Remapping Structures...

DMA Remapping Hardware Unit Definition (DRHD) Structure #1
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0018
Flags:          0x00  -- INCLUDE_ALL = no
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed90000
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1b Function: 0x00

DMA Remapping Hardware Unit Definition (DRHD) Structure #2
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0028
Flags:          0x00  -- INCLUDE_ALL = no
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed92000
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x02
    Device Scope Structure #3
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x03

Reserved Memory Region Reporting (RMRR) Structure #1
Type:           0x0001 (ACPI_DMAR_RMRR)
Length:         0x0058
Reserved:       0x0000
Segment Number: 0x0000
Base Address:   0xbeecc000
End Address:    0xbeecc000
    Device Scope Structure #1
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x00
    Device Scope Structure #2
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x01
    Device Scope Structure #3
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x02
    Device Scope Structure #4
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1d Function: 0x07
    Device Scope Structure #5
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x00
    Device Scope Structure #6
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x01
    Device Scope Structure #7
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x02
    Device Scope Structure #8
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1a Function: 0x07

==================================================
End DMAR

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

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

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Ross Philipson]

Did you mention in an earlier email that you have the latest BIOS for
this system?

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Stefan Bauer
Sent: Friday, October 31, 2008 12:20 PM
Cc: xen-devel@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Ross Philipson schrieb:
> Did you mention in an earlier email that you have the latest BIOS for
> this system?

The latest available from the lenovo webpage yes.

-- 
stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Ross Philipson]

That is a bummer. I am not really sure where to go with it. If there is
no DRHD for that device (or a number of other ones so it would seem)
then there is no way to setup DMA remapping for those devices. Maybe
someone else on the list has some ideas.

Ross

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

Ross Philipson schrieb:
> Did you mention in an earlier email that you have the latest BIOS for
> this system?

The latest available from the lenovo webpage yes.

-- 
stefan

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

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Ross Philipson schrieb:
> That is a bummer. I am not really sure where to go with it. If there is
> no DRHD for that device (or a number of other ones so it would seem)
> then there is no way to setup DMA remapping for those devices. Maybe
> someone else on the list has some ideas.

So if i understand you correctly, there is some problem with the PEG
graphic card in my case? Another graphic card might solve that problem?

Regards

-- 
stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Ross Philipson]

The dump of the DMAR on your system showed the individual remapping
hardware units and which PCI devices they handled. Here is an excerpt
(my comment prefixed with a **):

DMA Remapping Hardware Unit Definition (DRHD) Structure #1
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0018
Flags:          0x00  -- INCLUDE_ALL = no 
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed90000
    Device Scope Structure #1 ** This unit has one device scope entry
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x1b Function: 0x00 ** This unit support this
device/function on bus 0

DMA Remapping Hardware Unit Definition (DRHD) Structure #2
Type:           0x0000 (ACPI_DMAR_DRHD)
Length:         0x0028
Flags:          0x00  -- INCLUDE_ALL = no
Reserved:       0x00
Segment Number: 0x0000
Register Base:  0xfed92000
    Device Scope Structure #1 ** This unit has 3 device scope entries
each supporting one a different function on
device 3 bus 0
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x00 ** one function
    Device Scope Structure #2 ** another scope
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x02 ** another function
    Device Scope Structure #3 ** another scope
    ==========================
    Type:           0x01 (ACPI_DEV_ENDPOINT)
    Length:         0x08
    Reserved:       00 00
    Enumeration ID: 0x00 - Reserved
    Start Bus Num:  0x00
    Path Depth = 1, Path Entries:
       -- Device: 0x03 Function: 0x03 ** another function

Normally there is another DMA Remapping Hardware Unit Definition (DRHD)
that has the INCLUDE_ALL flag set and handles all devices that are not
specifically handled by DRHDs like the ones above (at least that has
been my experience though I haven't seen all that many machines). Your
system does not seem to have that. So there is no real way to setup DMA
remapping for any of the devices on your system that is not explicitly
represented above. My gut feeling is that it is a BIOS problem - the
ACPI tables are incorrect/incomplete but I cannot be sure.

If you use lspci you can see the (small) set of PCI devices that the
VT-d hardware seems to have DRHD units for. You might also want to
contact Lenovo and see if this is a known issue.

Thanks
Ross

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

Ross Philipson schrieb:
> That is a bummer. I am not really sure where to go with it. If there
is
> no DRHD for that device (or a number of other ones so it would seem)
> then there is no way to setup DMA remapping for those devices. Maybe
> someone else on the list has some ideas.

So if i understand you correctly, there is some problem with the PEG
graphic card in my case? Another graphic card might solve that problem?

Regards

-- 
stefan

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

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Ross Philipson schrieb:
> If you use lspci you can see the (small) set of PCI devices that the
> VT-d hardware seems to have DRHD units for. You might also want to
> contact Lenovo and see if this is a known issue.

I'm still trying to get in contact with lenovo to work that problem
out. Will keep you up to date with news from that side.

Regards
-- 
stefan

RE: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Han, Weidong]

Stefan Bauer wrote:
> Ross Philipson schrieb:
>> That is a bummer. I am not really sure where to go with it. If there
>> is no DRHD for that device (or a number of other ones so it would
>> seem) then there is no way to setup DMA remapping for those devices.
>> Maybe someone else on the list has some ideas.
> 
> So if i understand you correctly, there is some problem with the PEG
> graphic card in my case? Another graphic card might solve that
> problem? 
> 

You don't use PEG, so it is not related to it. The dump of the DMAR on your system shows definitely BIOS doesn't setup ACPI correctly for DMAR. Pls contact your vendor.

Regards,
Weidong

Re: iommu: mapping reserved region failed - Q35 -VT-DIssue

[Stefan Bauer]

Han, Weidong schrieb:
> Stefan Bauer wrote:
>> Ross Philipson schrieb:
>>> That is a bummer. I am not really sure where to go with it. If there
>>> is no DRHD for that device (or a number of other ones so it would
>>> seem) then there is no way to setup DMA remapping for those devices.
>>> Maybe someone else on the list has some ideas.
>> So if i understand you correctly, there is some problem with the PEG
>> graphic card in my case? Another graphic card might solve that
>> problem? 
>>
> 
> You don't use PEG, so it is not related to it. The dump of the DMAR on your system shows definitely BIOS doesn't setup ACPI correctly for DMAR. Pls contact your vendor.

My intention was to passthrough my PCI-E graphic card to the HVM domU,
so i definitely use a PEG-Card. I'm awaiting response from lenovo, but
as Rajesh mentioned, your ways to contact lenovo might be ways better
than mine.

Regards

-- 
stefan

RE: iommu: mapping reserved region failed - Q35 - VT-D Issue

[Kay, Allen M]

Can you put some printk's in domain_context_mapping() to see at which point it failed?

If it is a BIOS problem, it is possible this function cannot find the matching vt-d engine for this device.

Allen

>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com 
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>Stefan Bauer
>Sent: Wednesday, October 29, 2008 10:28 AM
>To: xen-devel@lists.xensource.com
>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@lists.xensource.com
>http://lists.xensource.com/xen-devel
>

Re: iommu: mapping reserved region failed - Q35 - VT-D Issue

[Stefan Bauer]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Kay, Allen M schrieb:
> Can you put some printk's in domain_context_mapping() to see at which point it failed?
> 
> If it is a BIOS problem, it is possible this function cannot find the matching vt-d engine for this device.

Allen,

unfortunately i'm not familiar with any higher programming language.
Please see attached a bit more verbose informations generated by PCI
Backend Debugging in the kernel:

For example:

pciback 0000:00:19.0: probing...
BUG: warning at
/usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a

get's me an unavailable network controller which has the 0000:00:19.0
address.

-- 
Stefan

[-- Attachment #2: xen-dmesg --]
[-- Type: text/plain, Size: 17245 bytes --]

Bootdata ok (command line is root=/dev/sda2 ro pciback.hide=(01:00.0))
Linux version 2.6.18.8-xen (root@xen64) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #2 SMP Wed Oct 29 20:59:53 CET 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000020800000 (usable)
DMI present.
On node 0 totalpages: 128565
  DMA zone: 1305 pages, LIFO batch:0
  DMA32 zone: 127260 pages, LIFO batch:31
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: LENOVO   Product ID: THINKCEN APIC at: 0xFEE00000
I/O APIC #2 Version 32 at 0xFEC00000.
Setting APIC routing to xen
Processors: 2
Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
Built 1 zonelists.  Total pages: 128565
Kernel command line: root=/dev/sda2 ro pciback.hide=(01:00.0)
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2327.514 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB enabled: 
 Aperture:     64 megabytes
 Kernel range: ffff8800018fd000 - ffff8800058fd000
 Address size: 27 bits
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Memory: 438812k/532480k available (1699k kernel code, 85336k reserved, 734k data, 136k init)
Calibrating delay using timer specific routine.. 4656.97 BogoMIPS (lpj=23284873)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Freeing SMP alternatives: 24k freed
GSI 16 sharing vector 0xA8 and IRQ 16
GSI 17 sharing vector 0xB0 and IRQ 17
GSI 18 sharing vector 0xB8 and IRQ 18
GSI 19 sharing vector 0xC0 and IRQ 19
GSI 20 sharing vector 0xC8 and IRQ 20
Brought up 2 CPUs
Initializing CPU#1
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
migration_cost=12
Unpacking initramfs... done
Freeing initrd memory: 5537k freed
PM: Adding info for No Bus:platform
NET: Registered protocol family 16
PM: Adding info for No Bus:xen
PM: Adding info for No Bus:xen-backend
PCI: Using configuration type 1
xen_mem: Initialising balloon driver.
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PM: Adding info for No Bus:pci0000:00
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.2
Boot video device is 0000:11:0c.0
PCI: Transparent bridge - 0000:00:1e.0
PM: Adding info for pci:0000:00:00.0
PM: Adding info for pci:0000:00:01.0
PM: Adding info for pci:0000:00:03.0
PM: Adding info for pci:0000:00:03.2
PM: Adding info for pci:0000:00:03.3
PM: Adding info for pci:0000:00:19.0
PM: Adding info for pci:0000:00:1a.0
PM: Adding info for pci:0000:00:1a.1
PM: Adding info for pci:0000:00:1a.2
PM: Adding info for pci:0000:00:1a.7
PM: Adding info for pci:0000:00:1b.0
PM: Adding info for pci:0000:00:1d.0
PM: Adding info for pci:0000:00:1d.1
PM: Adding info for pci:0000:00:1d.2
PM: Adding info for pci:0000:00:1d.7
PM: Adding info for pci:0000:00:1e.0
PM: Adding info for pci:0000:00:1f.0
PM: Adding info for pci:0000:00:1f.2
PM: Adding info for pci:0000:00:1f.3
PM: Adding info for pci:0000:00:1f.5
PM: Adding info for pci:0000:01:00.0
PM: Adding info for pci:0000:11:0c.0
PCI->APIC IRQ transform: 0000:00:01.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:03.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:03.2[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:03.3[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:19.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1a.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1a.1[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1a.2[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:1a.7[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:1b.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1d.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1d.1[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1d.2[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:1d.7[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:1f.2[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1f.3[B] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:1f.5[C] -> IRQ 18
PCI->APIC IRQ transform: 0000:01:00.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:11:0c.0[A] -> IRQ 20
pciback: wants to seize 0000:01:00.0
pciback 0000:00:00.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:01.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:03.0: probing...
pciback 0000:00:03.2: probing...
pciback 0000:00:03.3: probing...
pciback 0000:00:19.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1a.0: probing...
pciback 0000:00:1a.1: probing...
pciback 0000:00:1a.2: probing...
pciback 0000:00:1a.7: probing...
pciback 0000:00:1b.0: probing...
pciback 0000:00:1d.0: probing...
pciback 0000:00:1d.1: probing...
pciback 0000:00:1d.2: probing...
pciback 0000:00:1d.7: probing...
pciback 0000:00:1e.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.2: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.3: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:00:1f.5: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

pciback 0000:01:00.0: probing...
pciback 0000:01:00.0: seizing device
pciback 0000:01:00.0: pcistub_device_alloc
pciback 0000:01:00.0: deferring initialization
pciback 0000:11:0c.0: probing...
BUG: warning at /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:31/pci_bus_probe_wrapper()

Call Trace:
 [<ffffffff8030cee1>] pci_bus_probe_wrapper+0x8f/0x9a
 [<ffffffff803049e8>] driver_probe_device+0x52/0xa8
 [<ffffffff80304b17>] __driver_attach+0x6d/0xaa
 [<ffffffff80304aaa>] __driver_attach+0x0/0xaa
 [<ffffffff803043e9>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80304047>] bus_add_driver+0x7e/0x130
 [<ffffffff802e9519>] __pci_register_driver+0x57/0x7d
 [<ffffffff80493d12>] pcistub_init+0xfb/0x1c9
 [<ffffffff80207158>] init+0x13e/0x34c
 [<ffffffff8020ae8c>] child_rip+0xa/0x12
 [<ffffffff8020701a>] init+0x0/0x34c
 [<ffffffff8020ae82>] child_rip+0x0/0x12

PCI: Failed to allocate mem resource #6:20000@d0000000 for 0000:01:00.0
PCI: Bridge: 0000:00:01.0
  IO window: 2000-2fff
  MEM window: d0000000-d2ffffff
  PREFETCH window: c0000000-cfffffff
PCI: Bridge: 0000:00:1e.0
  IO window: disabled.
  MEM window: d4000000-d5ffffff
  PREFETCH window: d3000000-d30fffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 5, 131072 bytes)
TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 65536 bind 32768)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1225311461.095:1): initialized
audit: cannot initialize inotify handle
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
pciback: pcistub_init_devices_late
pciback 0000:01:00.0: initializing...
pciback 0000:01:00.0: initializing config
pciback 0000:01:00.0: initializing virtual configuration space
pciback 0000:01:00.0: added config field at offset 0x04
pciback 0000:01:00.0: added config field at offset 0x3c
pciback 0000:01:00.0: added config field at offset 0x3d
pciback 0000:01:00.0: added config field at offset 0x0c
pciback 0000:01:00.0: added config field at offset 0x0d
pciback 0000:01:00.0: added config field at offset 0x0f
pciback 0000:01:00.0: added config field at offset 0x10
pciback 0000:01:00.0: added config field at offset 0x14
pciback 0000:01:00.0: added config field at offset 0x18
pciback 0000:01:00.0: added config field at offset 0x1c
pciback 0000:01:00.0: added config field at offset 0x20
pciback 0000:01:00.0: added config field at offset 0x24
pciback 0000:01:00.0: added config field at offset 0x30
pciback 0000:01:00.0: Found capability 0x1 at 0x60
pciback 0000:01:00.0: added config field at offset 0x60
pciback 0000:01:00.0: added config field at offset 0x62
pciback 0000:01:00.0: added config field at offset 0x64
pciback 0000:01:00.0: added config field at offset 0x66
pciback 0000:01:00.0: added config field at offset 0x67
pciback 0000:01:00.0: enabling device
PCI: Enabling device 0000:01:00.0 (0104 -> 0107)
pciback 0000:01:00.0: reset device
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PM: Adding info for platform:i8042
serio: i8042 AUX port at 0x60,0x64 irq 12
PM: Adding info for serio:serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
PM: Adding info for serio:serio1
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 1
NET: Registered protocol family 17
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 136k freed
input: AT Translated Set 2 keyboard as /class/input/input0
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1C40 irq 14
scsi0 : ata_piix
PM: Adding info for No Bus:host0
ata1.00: ATA-7, max UDMA/133, 156312576 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
PM: Adding info for No Bus:target0:0:0
  Vendor: ATA       Model: WDC WD800JD-08MS  Rev: 10.0
  Type:   Direct-Access                      ANSI SCSI revision: 05
PM: Adding info for scsi:0:0:0:0
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1C48 irq 15
scsi1 : ata_piix
PM: Adding info for No Bus:host1
ata2.00: ATAPI, max UDMA/33
ata2.00: configured for UDMA/33
PM: Adding info for No Bus:target1:0:0
  Vendor: TSSTcorp  Model: DVD-ROM TS-H353B  Rev: LE06
  Type:   CD-ROM                             ANSI SCSI revision: 05
PM: Adding info for scsi:1:0:0:0
ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ]
PCI: Setting latency timer of device 0000:00:1f.5 to 64
ata3: SATA max UDMA/133 cmd 0x1CB8 ctl 0x1CAE bmdma 0x1C60 irq 18
ata4: SATA max UDMA/133 cmd 0x1CB0 ctl 0x1CAA bmdma 0x1C68 irq 18
scsi2 : ata_piix
PM: Adding info for No Bus:host2
ATA: abnormal status 0x7F on port 0x1CBF
scsi3 : ata_piix
PM: Adding info for No Bus:host3
ATA: abnormal status 0x7F on port 0x1CB7
SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156312576 512-byte hdwr sectors (80032 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: Attached scsi disk sda
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
sr0: scsi3-mmc drive: 125x/125x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 1:0:0:0: Attached scsi generic sg1 type 5
Adding 289160k swap on /dev/sda3.  Priority:-1 extents:1 across:289160k
EXT3 FS on sda2, internal journal
usbcore: registered new driver usbkbd
/usr/src/linux-2.6.18-xen.hg/drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda5, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

[-- Attachment #3: xm-dmesg --]
[-- Type: text/plain, Size: 6002 bytes --]

 __  __            _____ _  _                      _        _     _      
 \ \/ /___ _ __   |___ /| || |     _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \    |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) |__   _|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_) |_|     \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.4-unstable (root@) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) Tue Oct 28 23:12:59 CET 2008
(XEN) Latest ChangeSet: Thu Oct 23 15:38:52 2008 +0100 18711:874d0d673ecb
(XEN) Command line: console=vga max_loop=128 dom0_mem=512M iommu=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e000 (usable)
(XEN)  000000000009e000 - 00000000000a0000 (reserved)
(XEN)  00000000000ca000 - 00000000000cc000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000beeb0000 (usable)
(XEN)  00000000beeb0000 - 00000000beec9000 (ACPI data)
(XEN)  00000000beec9000 - 00000000beecc000 (ACPI NVS)
(XEN)  00000000beecc000 - 00000000c0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN) System RAM: 3054MB (3127608kB)
(XEN) ACPI: RSDP 000F5E00, 0024 (r2 PTLTD )
(XEN) ACPI: XSDT BEEBD8CF, 00B4 (r1 LENOVO TC-2R     60400D0  LTP        0)
(XEN) ACPI: TCPA BEEC8B21, 0032 (r2 LENOVO TC-2R     60400D0 PTL         0)
(XEN) ACPI: FACP BEEC8B53, 00F4 (r3 INTEL            60400D0 PTL         3)
(XEN) ACPI: DSDT BEEC0FC8, 7AE5 (r1  INTEL BEARLAKE  60400D0 MSFT  100000E)
(XEN) ACPI: FACS BEECBFC0, 0040
(XEN) ACPI: DMAR BEEC8C47, 00C8 (r1 Intel  OEMDMAR   60400D0 LOHR        1)
(XEN) ACPI: SLIC BEEC8D0F, 0176 (r1 LENOVO TC-2R     60400D0  LTP        0)
(XEN) ACPI: MCFG BEEC8E85, 003C (r1 PTLTD    MCFG    60400D0  LTP        0)
(XEN) ACPI: HPET BEEC8EC1, 0038 (r1 PTLTD  HPETTBL   60400D0  LTP        1)
(XEN) ACPI: APIC BEEC8EF9, 0068 (r1 PTLTD  	 APIC    60400D0  LTP        0)
(XEN) ACPI: BOOT BEEC8F61, 0028 (r1 PTLTD  $SBFTBL$  60400D0  LTP        1)
(XEN) ACPI: ASF! BEEC8F89, 0077 (r16   CETP     CETP  60400D0 PTL         1)
(XEN) ACPI: SSDT BEEBF212, 025F (r1  PmRef  Cpu0Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBF16C, 00A6 (r1  PmRef  Cpu7Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBF0C6, 00A6 (r1  PmRef  Cpu6Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBF020, 00A6 (r1  PmRef  Cpu5Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBEF7A, 00A6 (r1  PmRef  Cpu4Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBEED4, 00A6 (r1  PmRef  Cpu3Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBEE2E, 00A6 (r1  PmRef  Cpu2Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBED88, 00A6 (r1  PmRef  Cpu1Tst     3000 INTL 20050228)
(XEN) ACPI: SSDT BEEBD983, 1405 (r1  PmRef    CpuPm     3000 INTL 20050228)
(XEN) Xen heap: 14MB (14704kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Intel VT-d has been enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2327.563 MHz processor.
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz stepping 0b
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz stepping 0b
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) [VT-D]iommu.c:1694:d32767 IOMMU: mapping reserved region failed
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x531ecc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   00000000b9000000->00000000ba000000 (126976 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff80531ecc
(XEN)  Init. ramdisk: ffffffff80532000->ffffffff80a9a600
(XEN)  Phys-Mach map: ffffffff80a9b000->ffffffff80b9b000
(XEN)  Start info:    ffffffff80b9b000->ffffffff80b9b4a4
(XEN)  Page tables:   ffffffff80b9c000->ffffffff80ba7000
(XEN)  Boot stack:    ffffffff80ba7000->ffffffff80ba8000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: ........................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 108kB init memory.
(XEN) [VT-D]iommu.c:1542:d0 intel_iommu_add_device: context mapping failed
(XEN) [VT-D]iommu.c:1542:d0 intel_iommu_add_device: context mapping failed
(XEN) printk: 8 messages suppressed.
(XEN) [VT-D]iommu.c:1542:d0 intel_iommu_add_device: context mapping failed

[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

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