All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander Eikelenboom <linux@eikelenboom.it>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir@xen.org>
Subject: Re: Re: Konrad devel/next-3.0, pci-passthrough not working: Error: pci: PCI Backend and pci-stub don't own device
Date: Tue, 21 Jun 2011 21:02:29 +0200	[thread overview]
Message-ID: <1284512453.20110621210229@eikelenboom.it> (raw)
In-Reply-To: <20110621170525.GA10328@dumpdata.com>


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 ?


>> 
>> --
>> Sander

  parent reply	other threads:[~2011-06-21 19:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 13:41 Konrad devel/next-3.0, pci-passthrough not working: Error: pci: PCI Backend and pci-stub don't own device Sander Eikelenboom
2011-06-21 14:13 ` Konrad Rzeszutek Wilk
2011-06-21 14:24   ` Sander Eikelenboom
2011-06-21 14:40   ` Sander Eikelenboom
2011-06-21 15:11   ` Sander Eikelenboom
2011-06-21 15:39     ` Sander Eikelenboom
2011-06-21 17:05     ` Konrad Rzeszutek Wilk
2011-06-21 17:17       ` Sander Eikelenboom
2011-06-21 19:02       ` Sander Eikelenboom [this message]
2011-06-22 14:00         ` Konrad Rzeszutek Wilk
2011-06-22 14:13           ` Sander Eikelenboom
2011-06-22 14:28             ` Konrad Rzeszutek Wilk
2011-06-22 15:17               ` Sander Eikelenboom
2011-06-27 15:26                 ` Konrad Rzeszutek Wilk
2011-06-27 17:09                   ` Sander Eikelenboom
2011-06-29  7:19               ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1284512453.20110621210229@eikelenboom.it \
    --to=linux@eikelenboom.it \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.