WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] with Xen4 config -> (pci-passthrough-strict-check no),

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: 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"
From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
Date: Fri, 29 Jan 2010 15:11:24 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, horms@xxxxxxxxxxxx, dexuan.cui@xxxxxxxxx
Delivery-date: Fri, 29 Jan 2010 15:11:37 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oLlkCrsgCFSenQcbMs4A117qcl6LHMWoHK7C1cjNhHk=; b=H0LD/YvJpu9H2UYXB5fHZL6LufHy3B9YZcAAwl1aufXt80La9DQ98Jmrl2Sx2xp6mv zSKBl91I5GKHwujg6NmDUEkDyrBu1CNgOM1I/fKgHdYk0oKw9f8S0oz8k5iEUHb7bkkQ uWWiyqIZPTtVQoPhAXK2eW6DmZxASQOMWRk50=
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 :cc:content-type:content-transfer-encoding; b=qDbUVXSR77yzGqwcgXHm7KPA6L1Cecyt7QXLv0ff34JdXsAfclKSkZ3phj8qf18xMr 2G51rO6WC/LS9pwCglg8tFLfUL2ds2wMyAey2cWuOP8L+Eg+MOzLVT4CK75l6nsY9SeM aY3RfCvOj/xb55nTMm+/H6MxEn6DMZFSh3IXQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100129224445.GA5852@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <c67eed301001291410w2c926730s6c2d7ce5e9c5d46b@xxxxxxxxxxxxxx> <20100129224445.GA5852@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I bleieve you have it backwards, no?

On Fri, Jan 29, 2010 at 2:44 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
>>       grep passthrough /etc/xen/xend-config.sxp
>>               (pci-passthrough-strict-check no)
>>       grep hide /etc/modprobe.d/99-local.conf
>>               options pciback hide=(0000:04:07.0)(0000:04: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:
>  xen-pciback.hide=(04:07.0)(04:06.0) pci=resource_alignment=04:07.0
>
>
>>
>> and checking,
>>
>>       lsmod | egrep -i "pciback|xen"
>>               pciback                54471  0
>>               xenbus_be               3474  4 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_module

"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=(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 ...)

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