xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: 0bo0 <0.bugs.only.0@gmail.com>
To: xen-devel@lists.xensource.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: Mon, 1 Feb 2010 10:28:27 -0800	[thread overview]
Message-ID: <c67eed301002011028p4c90c716ld140b75d7275469@mail.gmail.com> (raw)
In-Reply-To: <c67eed301002010857v5d554ac0i8e84c72539b158a0@mail.gmail.com>

for anyone interested,

upgrading openSUSE 11.2's kernel from 2.6.33-rc5-4-xen x86_64 ->
2.6.33-rc5-5-xen x86_64 fixed the problem reported here.  @ DomU, now,
 boots fine and the shared-bus PCI card is properly passedthrough.
dropping back to verify, and the problem returns.

the instructions @ wiki remain correct, and -- for kernel with pciback
compiled as module -- the command line options suggested (
xen-pciback.hide=(04:07.0)(04:06.0) pci=resource_alignment) do NOT
work.  rather the /etc/modprobe* config additions, along with the
usual (guestdev=0000:04:07.0,0000:04:06.0 reassign_resources) works as
it always has, consistente with the documentation.

hth.

thanks.

  reply	other threads:[~2010-02-01 18:28 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
2010-01-29 23:11   ` 0bo0
2010-02-01 16:57     ` 0bo0
2010-02-01 18:28       ` 0bo0 [this message]
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=c67eed301002011028p4c90c716ld140b75d7275469@mail.gmail.com \
    --to=0.bugs.only.0@gmail.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 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).