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

[0bo0 <0.bugs.only.0@gmail.com>]

I bleieve you have it backwards, no?

On Fri, Jan 29, 2010 at 2:44 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> 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 ...)