From mboxrd@z Thu Jan 1 00:00:00 1970 From: 0bo0 <0.bugs.only.0@gmail.com> Subject: Re: with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don't own device" Date: Fri, 29 Jan 2010 15:11:24 -0800 Message-ID: References: <20100129224445.GA5852@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100129224445.GA5852@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com, horms@verge.net.au, dexuan.cui@intel.com List-Id: xen-devel@lists.xenproject.org I bleieve you have it backwards, no? On Fri, Jan 29, 2010 at 2:44 PM, Konrad Rzeszutek Wilk wrote: >> =A0 =A0 =A0 grep passthrough /etc/xen/xend-config.sxp >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 (pci-passthrough-strict-check no) >> =A0 =A0 =A0 grep hide /etc/modprobe.d/99-local.conf >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 options pciback hide=3D(0000:04:07.0)(0000:0= 4:06.0) > > That won't work. That option is only useful if pciback is compiled > in the kernel. To be exact, you would need this in your bootline > argument: > =A0xen-pciback.hide=3D(04:07.0)(04:06.0) pci=3Dresource_alignment=3D04:07= .0 > > >> >> and checking, >> >> =A0 =A0 =A0 lsmod | egrep -i "pciback|xen" >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 pciback =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A054471= =A00 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 xenbus_be =A0 =A0 =A0 =A0 =A0 =A0 =A0 3474 = =A04 netbk,blkbk,blktap,pciback > > Since it is module you need to follow the documentation about how to > seize and bind using pciback. Google is your friend. > reading @ http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_m= odule "If the Dom0 XenLinux kernel is built with pciback as a module, attempting to use the kernel command-line parameter pciback.hide won't work. ' ... "If the Dom0 XenLinux kernel is built with pciback as a module, attempting to use the kernel command-line parameter pciback.hide won't work. This includes loading pciback in an initrd. This means that if you wish to assign hardware to a DomU another method is needed. There are two possibilities. ..." since Dom0 is, apparently, "built with pciback as a module", the wiki specifically instructs: Add a line to /etc/modprobe.conf to pass the hide parameter to pciback options pciback hide=3D(0000:05:02.0) You'll also note, from the dmesg output i'd included above, that there's no problem seizing the *1st* card, configured in the same manner. and, all of this worked just fine before the most recent Xen4 update (this morning ...)