Mike Viau
2013-Mar-17 19:35 UTC
[Pkg-xen-devel] Bug#703266: Xen PCI passthrough: PCI Backend and pci-stub don't own sibling device 0000:00:00.0
Package: xen-utils-4.1 Version: 4.1.4-2 Severity: normal -- System Information: Debian Release: 7.0 ? APT prefers testing ? APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-utils-4.1 depends on: ii? e2fslibs????????? 1.42.5-1 ii? libc6???????????? 2.13-38 ii? libgnutls26?????? 2.12.20-4 ii? libncurses5?????? 5.9-10 ii? libpci3?????????? 1:3.1.9-6 ii? libtinfo5???????? 5.9-10 ii? libuuid1????????? 2.20.1-5.3 ii? libxen-4.1??????? 4.1.4-2 ii? libxenstore3.0??? 4.1.4-2 ii? python??????????? 2.7.3-4 ii? python2.7???????? 2.7.3-6 ii? xen-utils-common? 4.1.4-2 ii? zlib1g??????????? 1:1.2.7.dfsg-13 Versions of packages xen-utils-4.1 recommends: ii? bridge-utils?????????????????????????????????? 1.5-6 ii? qemu-keymaps?????????????????????????????????? 1.1.2+dfsg-5 ii? qemu-utils???????????????????????????????????? 1.1.2+dfsg-5 ii? xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1]? 4.1.4-2 Versions of packages xen-utils-4.1 suggests: pn? xen-docs-4.1? <none> -- no debconf information -- Notes: This bug is identical to Ubuntu's LaunchPad Bug #941220. Additionally a snip from xend.log: Traceback (most recent call last): ? File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 106, in create ??? vm.start() ? File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start ??? XendTask.log_progress(31, 60, self._initDomain) ? File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress ??? retval = func(*args, **kwds) ? File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2925, in _initDomain ??? raise exn VmError: pci: PCI Backend and pci-stub don't own sibling device 0000:00:00.0 of device 0000:04:00.1 Thanks.
Maybe Matching Threads
- Bug#703266: Xen PCI passthrough: PCI Backend and pci-stub don't own sibling device 0000:00:00.0
- domUs doesn''t boot after upgrade to xen 3.2
- SETVCPUCONTEXT failed
- SETVCPUCONTEXT failed
- Xen+drbd VmError: Block device must have "phy", "file" or "tap" specified to type