RE: [Xen-devel] Fwd: Cannot assign device in Xen-unstable [VT-d]
Can you paste your serial console output? I want to see
whether the hidden devices are really assigned to dom0 via add_device
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Bryan
Sent: 2008年8月10日 15:42
Subject: [Xen-devel] Fwd: Cannot assign
device in Xen-unstable [VT-d]
Moving over to xen-devel to see if anyone has any suggestions
Thanks again to everyone for the help earlier with my VT-d kernel
---------- Forwarded message ----------
From: Bryan York <bryan.york@xxxxxxxxx>
Fri, Aug 8, 2008 at 5:35 PM
Subject: Cannot assign device in Xen-unstable
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.
/vmlinuz-2.6.18-92.el5.xenpcibackxen ro root=/dev/VolGroup00/LogVol00
xm create hd.hvm
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.
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.)
Xen-devel mailing list