[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Fwd: Cannot assign device in Xen-unstable [VT-d]

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Bryan York" <bryan.york@xxxxxxxxx>
  • Date: Sun, 10 Aug 2008 00:42:22 -0700
  • Delivery-date: Sun, 10 Aug 2008 00:42:52 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=RijWPCewRjZ6/M3jxi2H+P8aX2ebCG3cRmrSlR/lyG2PVzlKe0ZP69L6flWlR07nB8 ePkkYsuZpgHKQ14k7NywtOEntSPsQyaGDs4V2yCLtPu3rjtW2+mCtoWD8HA2VDxNrHHI CiJhttQogXzyTkz8x+pk2rjCOC9D4GyCV0x7k=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Moving over to xen-devel to see if anyone has any suggestions there.

Thanks again to everyone for the help earlier with my VT-d kernel hangs.


---------- Forwarded message ----------
From: Bryan York <bryan.york@xxxxxxxxx>
Date: Fri, Aug 8, 2008 at 5:35 PM
Subject: Cannot assign device in Xen-unstable [VT-d]
To: xen-users@xxxxxxxxxxxxxxxxxxx


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?



Attachment: xmdmesg
Description: Binary data

Attachment: dmesg
Description: Binary data

Attachment: hd.hvm
Description: Binary data

Attachment: lspci
Description: Binary data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.