[Xen-users] RE: Xen4 / Intel DX58SO Mobo / VT-d not working

[chris <tknchris@xxxxxxxxx>]

When reading the vtdhowto I noticed the ability to set iommu=verbose.
Here is that output, I don't know if it helps at all to figure out
what is wrong.


---------- Forwarded message ----------
From: chris <tknchris@xxxxxxxxx>
Date: Wed, May 12, 2010 at 5:28 PM
Subject: Xen4 / Intel DX58SO Mobo / VT-d not working
To: Xen-Users List <xen-users@xxxxxxxxxxxxxxxxxxx>


Hello,

I've previously been successful with Xen4 and VT-d on other systems. I
am having trouble getting VT-d passthrough working to a WinXP domain
with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios,
xm info shows hvm_directio capability, I have iommu=1 set, I have the
devices bound to pciback on dom0 cmdline, xm
pci-list-assignable-devices shows the devices as assignable. When I
attempt to start the VM I get the error:

Error: Failed to assign device to IOMMU
(0000:02:00.0@100,msitranslate=1,power_mgmt=0)

Below is all the information I can think of that would be useful to
help debug it:

BIOS VT-d Enabled:
http://i43.tinypic.com/nl3a5e.jpg
http://i42.tinypic.com/nqvlu1.jpg

grub entry:

title           Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13
root            (hd0,0)
kernel          /boot/xen-4.0.0.gz iommu=1 dom0_mem=256M
dom0_max_vcpus=1 dom0_vcpus_pin=true
module          /boot/vmlinuz-2.6.31.13 root=/dev/md0 ro console=tty0
xen-pciback.permissive
xen-pciback.hide=(02:00.0)(02:00.1)(02:00.2)(04:00.0)(04:00.1)(04:00.2)(07:00.0)(07:00.1)(07:00.2)(09:00.0)(09:00.1)(09:00.2)
module          /boot/initrd.img-2.6.31.13

# xm pci-list-assignable-devices
0000:09:00.0
0000:09:00.1
0000:09:00.2
0000:07:00.0
0000:07:00.1
0000:07:00.2
0000:04:00.0
0000:04:00.1
0000:04:00.2
0000:02:00.0
0000:02:00.1
0000:02:00.2

# xm info
host                   : test-box2
release                : 2.6.31.13
version                : #2 SMP Wed May 12 14:11:37 EDT 2010
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2800
hw_caps                :
bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 7950
free_memory            : 7812
node_to_cpu            : node0:0-7
node_to_memory         : node0:7812
node_to_dma32_mem      : node0:3249
max_node_id            : 0
xen_major              : 4
xen_minor              : 0
xen_extra              : .0
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : iommu=1 dom0_mem=256M dom0_max_vcpus=1
dom0_vcpus_pin=true
cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
cc_compile_by          : root
cc_compile_domain      :
cc_compile_date        : Thu May  6 13:41:25 EDT 2010
xend_config_format     : 4

# xm create vm-five.cfg
Using config file "./vm-five.cfg".
Error: Failed to assign device to IOMMU
(0000:02:00.0@100,msitranslate=1,power_mgmt=0)

I feel like I'm missing something really obvious but I've been at it
for a while now and have run out of brain power. Anyone have any idea
what might be wrong?

- chris

xm-dmesg-vtd-verbose.txt
Description: Text document

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