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-users

Re: [Xen-users] pci device not owned by pciback.

> What Xen version are you using? Are you using a pvops based kernel? Or a
> 'classic' xen kernel based on 2.6.18+patches?
> Are you sure it mentions the exact same id twice? It is more likely to
> report two almost identical ids, with a small difference in the last
> digit... (e.g. 0000:0e:04.1 must be co-assigned with 0000:0e:04.0)

That was a copy and paste of the output, and double checked. It says the
same one. There is another as you suspected.

Running xen 3.4 for SLES11. Not sure this is enough to answer your
question:
Linux test03 2.6.27.19-5-xen #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 
x86_64 GNU/Linux

> Hiding is the same for VTd and for PV. However, the 'co-assigned' error
> message is typical for VTd, it doesn't allow devices on the same PCI bus
> to be divided over more than one vm.
> If you are passing through a single device to a PV machine, and xen gives
> you the above mentioned 'co-assigned' error, it is probably due to a bug
> in xen (which appeared a while ago, but has since been fixed).

This sounds like the bug. 

Thanks,
James


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