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

Re: [Xen-devel] with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don't own device"


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
  • Date: Mon, 1 Feb 2010 10:28:27 -0800
  • Delivery-date: Mon, 01 Feb 2010 10:28:48 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=FSnouWNVN82ni/TO9IW/H45/DVHlvADBmhPY3jBGhpV19xcZRnbhe7jfulA8jQMkMz 5sTty+SAcE0TRUG4Tqk00jtrmaCz0MZb+YeTTKUZY3W+03xJgI18oJUydhIujcnRwDk2 AiKz7gwMaIsoyajeiPUbZuBnsyx3AfdqY+6i4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

for anyone interested,

upgrading openSUSE 11.2's kernel from 2.6.33-rc5-4-xen x86_64 ->
2.6.33-rc5-5-xen x86_64 fixed the problem reported here.  @ DomU, now,
 boots fine and the shared-bus PCI card is properly passedthrough.
dropping back to verify, and the problem returns.

the instructions @ wiki remain correct, and -- for kernel with pciback
compiled as module -- the command line options suggested (
xen-pciback.hide=(04:07.0)(04:06.0) pci=resource_alignment) do NOT
work.  rather the /etc/modprobe* config additions, along with the
usual (guestdev=0000:04:07.0,0000:04:06.0 reassign_resources) works as
it always has, consistente with the documentation.

hth.

thanks.

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


 


Rackspace

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