[Xen-users] Cannot assign device in Xen-unstable [VT-d]

["Bryan York" <bryan.york@xxxxxxxxx>]

Hello,

I FINALLY got Xen working with VT-d. I compiled Xen-unstable (3.3) from Mercurial on CentOS 5.2, but compiled my own kernel-xen from the latest CentOS SRPM. (Made sure pciback was built-in and not a module, as the stock kernel-xen has it as a module.) I'm probably going to write a how-to soon, so stay tuned!

I have a JMicron SATA/PATA PCI Express controller with a DQ35JO motherboard and a Q6600 processor.

My grub entry:

title CentOS (2.6.18-92.el5.xenpcibackxen)
        root (hd0,0)
        kernel /xen-3.3.0-rc4-pre.gz vtd=1 iommu=1
        module /vmlinuz-2.6.18-92.el5.xenpcibackxen ro root=/dev/VolGroup00/LogVol00 pci=nommconf rhgb pciback.hide=(01:00.0)(01:00.1)
        module /initrd-2.6.18-92.el5.xenpcibackxen.img

xm create hd.hvm
Using config file "./hd.hvm".
Error: fail to assign device(1:0.1): maybe it has already been assigned to other domain, or maybe it doesn't exist.

My dmesg, xm dmesg, hvm, and lspci -vv are attached. What's weird is that Xen appears to be able to tell it grabbed 01:00.0. However I cannot grab just 01:00.0 because it is on the same PCI Express bus. I thought the problem initially was the fact that the JMB363 ide chipset was being picked up by the generic ATA driver, so I removed that and recompiled, but that didn't change anything. pciback.hide seems to grab both controllers per my dmesg. (They are on the same board.)

Any ideas?

Thanks,

-Bryan

Attachment: xmdmesg
Description: Binary data

Attachment: dmesg
Description: Binary data

Attachment: hd.hvm
Description: Binary data

Attachment: lspci
Description: Binary data

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