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

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Tue, Jun 21, 2011 at 09:02:29PM +0200, Sander Eikelenboom wrote:
> 
> Tuesday, June 21, 2011, 7:05:25 PM, you wrote:
> 
> > On Tue, Jun 21, 2011 at 05:11:42PM +0200, Sander Eikelenboom wrote:
> >> Hello Konrad,
> >> 
> >> Tuesday, June 21, 2011, 4:13:55 PM, you wrote:
> >> 
> >> > On Tue, Jun 21, 2011 at 03:41:26PM +0200, Sander Eikelenboom wrote:
> >> >> Hi Konrad,
> >> >> 
> >> >> I'm trying to use a kernel compiled from your devel/next-3.0 branch.
> >> 
> >> > Ok, good.
> >> >> 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
> >> 
> >> Ah it seems to be the sysfs indeed, in
> >> module name: xen_pciback
> >> driver:      xen-pciback
> 
> > This is above (and the sysfs below) is 2.6.39 based and it worked?
> >> 
> >> in 3.0 the
> >> module name: xen_pciback
> >> driver:      pciback
> >> 
> >> Quite a mix of names, and different use of minus and underscore.
> 
> > Hmm, you are a right. I somehow I thought I backed up the patch that
> > used the wrong name (well, not wrong but just incorrect).
> 
> So if I understand you correct you will revert the driver name from 
> xen-pciback to pciback, so no xen change is needed ?

So this patch:
f3fc28d52f42220bcce8c2fed12aef2a88c9fadc

    xen/pciback: revert the name of the PCI driver to 'pciback'.

should have done the trick but I am not seeing it in the
devel/xen-pciback-0.6.. Aha! I forgot to push the branch up to git.kernel.org.

Before I do that, can you cherry-pick that one please and tell
me if it works? If it does I will stick 'Reported-by' and 'Tested-by'
on the patch if you are OK with that.

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