xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: 0bo0 <0.bugs.only.0@gmail.com>
Cc: xen-devel@lists.xensource.com, horms@verge.net.au, dexuan.cui@intel.com
Subject: Re: with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don't own device"
Date: Fri, 29 Jan 2010 17:44:45 -0500	[thread overview]
Message-ID: <20100129224445.GA5852@phenom.dumpdata.com> (raw)
In-Reply-To: <c67eed301001291410w2c926730s6c2d7ce5e9c5d46b@mail.gmail.com>

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

  parent reply	other threads:[~2010-01-29 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 22:10 with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don't own device" 0bo0
2010-01-29 22:36 ` 0bo0
2010-01-29 22:44 ` Konrad Rzeszutek Wilk [this message]
2010-01-29 23:11   ` 0bo0
2010-02-01 16:57     ` 0bo0
2010-02-01 18:28       ` 0bo0
2010-02-01 18:58         ` Pasi Kärkkäinen
2010-02-01 19:21           ` 0bo0

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=20100129224445.GA5852@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=0.bugs.only.0@gmail.com \
    --cc=dexuan.cui@intel.com \
    --cc=horms@verge.net.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).