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: Fri, 29 Jan 2010 14:36:28 -0800 [thread overview]
Message-ID: <c67eed301001291436u54b21b9cr1fffd4488bc5057c@mail.gmail.com> (raw)
In-Reply-To: <c67eed301001291410w2c926730s6c2d7ce5e9c5d46b@mail.gmail.com>
checking @ source,
...
# Test whether the device is owned by pciback or pci-stub.
try:
pci_device = PciDevice(new_dev)
except Exception, e:
raise VmError("pci: failed to locate device and "+
"parse its resources - "+str(e))
if pci_device.driver!='pciback' and pci_device.driver!='pci-stub':
raise VmError(("pci: PCI Backend and pci-stub don't own device %s")\
%pci_device.name)
...
verifying the device is being seized @ startup; looks not to be :-/
...
dmesg | egrep "4:06|4:07|pciback"
...
[ 0.216794] PCI: 0000:04:07.0 has been reserved for guest domain.
[ 0.216794] PCI: 0000:04:06.0 has been reserved for guest domain.
[ 0.260161] pci 0000:04:06.0: reg 10: [mem 0xfbfe0000-0xfbffffff]
[ 0.260171] pci 0000:04:06.0: reg 14: [mem 0xfbfc0000-0xfbfdffff]
[ 0.260180] pci 0000:04:06.0: reg 18: [io 0xec00-0xec3f]
[ 0.260214] pci 0000:04:06.0: reg 30: [mem 0xfbfa0000-0xfbfbffff pref]
[ 0.260221] pci 0000:04:06.0: Disabling memory decoding and
releasing memory resources.
[ 0.260262] pci 0000:04:06.0: PME# supported from D0 D3hot D3cold
[ 0.260268] pci 0000:04:06.0: PME# disabled
[ 0.260340] pci 0000:04:07.0: reg 10: [mem 0xfbf9fc00-0xfbf9fc7f 64bit]
[ 0.260357] pci 0000:04:07.0: reg 18: [mem 0xfbf90000-0xfbf97fff 64bit]
[ 0.260367] pci 0000:04:07.0: reg 20: [io 0xe880-0xe88f]
[ 0.260385] pci 0000:04:07.0: reg 30: [mem 0xfbf00000-0xfbf7ffff pref]
[ 0.260391] pci 0000:04:07.0: Disabling memory decoding and
releasing memory resources.
[ 0.260434] pci 0000:04:07.0: supports D1 D2
[ 0.273957] pci 0000:04:07.0: BAR 6: assigned [mem
0xf0100000-0xf017ffff pref]
[ 0.273961] pci 0000:04:06.0: BAR 0: assigned [mem 0xfbf00000-0xfbf1ffff]
[ 0.273972] pci 0000:04:06.0: BAR 0: set to [mem
0xfbf00000-0xfbf1ffff] (PCI address [0xfbf00000-0xfbf1ffff]
[ 0.273977] pci 0000:04:06.0: BAR 1: assigned [mem 0xfbf20000-0xfbf3ffff]
[ 0.273985] pci 0000:04:06.0: BAR 1: set to [mem
0xfbf20000-0xfbf3ffff] (PCI address [0xfbf20000-0xfbf3ffff]
[ 0.273991] pci 0000:04:06.0: BAR 6: assigned [mem
0xf0180000-0xf019ffff pref]
[ 0.273995] pci 0000:04:07.0: BAR 2: assigned [mem
0xfbf40000-0xfbf47fff 64bit]
[ 0.274008] pci 0000:04:07.0: BAR 2: set to [mem
0xfbf40000-0xfbf47fff 64bit] (PCI address [0xfbf40000-0xfbf47fff]
[ 0.274013] pci 0000:04:07.0: BAR 0: assigned [mem
0xfbf48000-0xfbf4807f 64bit]
[ 0.274026] pci 0000:04:07.0: BAR 0: set to [mem
0xfbf48000-0xfbf4807f 64bit] (PCI address [0xfbf48000-0xfbf4807f]
[ 5.562894] sata_sil24 0000:04:07.0: version 1.1
[ 5.562913] sata_sil24 0000:04:07.0: enabling device (019d -> 019f)
[ 5.562933] sata_sil24 0000:04:07.0: PCI INT A -> GSI 21 (level,
low) -> IRQ 21
[ 29.932444] pciback 0000:04:06.0: seizing device
[ 29.932501] pciback 0000:04:06.0: enabling device (0115 -> 0117)
[ 29.932521] pciback 0000:04:06.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 29.932528] pciback 0000:04:06.0: PCI INT A disabled
dropping back to
uname -ri
2.6.31.12-2-xen x86_64
the dmesg output and the DomU init results are the same ... no-go.
next prev parent reply other threads:[~2010-01-29 22:36 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 [this message]
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
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=c67eed301001291436u54b21b9cr1fffd4488bc5057c@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).