[Xen-devel] Konrad devel/next-3.0, pci-passthrough not working: Error: pci: PCI Backend and pci-stub don't own device

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Hi Konrad,

I'm trying to use a kernel compiled from your devel/next-3.0 branch.
But trying to start a PV guest with pci-passthrough makes xen complain:

xm create /etc/xen/domU/production/security.cfg
Using config file "/etc/xen/domU/production/security.cfg".
Error: pci: PCI Backend and pci-stub don't own device 0000:04:00.0

Although the device is in fact owned by xen-pciback:

04:00.0 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback
04:00.1 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback
04:00.2 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback
04:00.3 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback
04:00.4 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback
04:00.5 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback
04:00.6 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback
04:00.7 USB Controller: NetMos Technology MCS9990 PCIe to 4âPort USB 2.0 Host 
Controller
        Subsystem: Device a000:4000
        Kernel driver in use: xen-pciback


With the kernels from Jeremy's tree (2.6.32.35) it works fine, using the exact 
same grub config lines with the 3.0 it doesn't.
All guests with pci-passthrough fail to start, all others start fine.
As hypervisor i'm running 4.1.1.

info attachted:
- xm info
- xm dmesg
- dmesg
- lspci

--
Sander

Attachment: dmesg.txt
Description: Text document

Attachment: lspci.txt
Description: Text document

Attachment: xm-dmesg.txt
Description: Text document

Attachment: xm-info.txt
Description: Text document

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