[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-bugs] [Bug 1340] New: 3.3.0 PCI devices ... must be co-assigned to the same guest



http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1340

           Summary: 3.3.0 PCI devices ... must be co-assigned to the same
                    guest
           Product: Xen
           Version: 3.0 (general)
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: xenbugs@xxxxxxxxxxxxxx


With 3.2.0 I passed through two PCI cards to a linux domU, now with 3.3.0 I am
unable to pass them, I receive this error on creating the domU

pci: 0000:08:03.0 must be co-assigned to the same guest with 0000:08:00.0

Seems to relate to this changeset
http://xenbits.xensource.com/xen-3.3-testing.hg?rev/e61978c24d84

My machine is not vt-d enabled, here is the "lspci -v" output for the devices
involved, the firewire device is on the motherboard and unrelated to the two
tuner cards.

08:00.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
       Subsystem: Compro Technology, Inc. Videomate DVB-T200
       Flags: medium devsel, IRQ 16
       Memory at febffc00 (32-bit, non-prefetchable) [disabled] [size=1K]
       Capabilities: [40] Power Management version 1

08:01.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
       Subsystem: Compro Technology, Inc. Videomate DVB-T200
       Flags: medium devsel, IRQ 17
       Memory at febff800 (32-bit, non-prefetchable) [disabled] [size=1K]
       Capabilities: [40] Power Management version 1

08:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev c0) (prog-if 10 [OHCI])
       Subsystem: ASUSTeK Computer Inc. Unknown device 81fe
       Flags: bus master, medium devsel, latency 64, IRQ 19
       Memory at febff000 (32-bit, non-prefetchable) [size=2K]
       I/O ports at ec00 [size=128]
       Capabilities: [50] Power Management version 2

Here is the "lspci -t" output

-[0000:00]-+-00.0
           +-01.0-[0000:01]--+-00.0
           |                 \-00.1
           +-1a.0
           +-1a.1
           +-1a.2
           +-1a.7
           +-1b.0
           +-1c.0-[0000:05-07]--+-00.0-[0000:07]----01.0
           |                    \-00.1-[0000:06]--
           +-1c.2-[0000:04]----00.0
           +-1c.3-[0000:03]----00.0
           +-1c.4-[0000:02]----00.0
           +-1d.0
           +-1d.1
           +-1d.2
           +-1d.7
           +-1e.0-[0000:08]--+-00.0
           |                 +-01.0
           |                 \-03.0
           +-1f.0
           +-1f.2
           \-1f.3

Is it really intended that all devices behind a PCI bridge have to be assigned
together to a domU? Or is my motherboard (ASUS P5E-WS-PRO) unusual in grouping
the PCI devices like this?


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.