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

[Xen-devel] follow up to a pciback "pv pci-passthrough co-assigned problem"


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: mail ignored <0.bugs.only.0@xxxxxxxxx>
  • Date: Fri, 22 Jan 2010 17:32:46 -0800
  • Cc: weidong.han@xxxxxxxxx
  • Delivery-date: Fri, 22 Jan 2010 17:33:09 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=d4JGRe9q+ZQUJXUZFCbKGOMx4DbfwXGnapHBm4HR55Gg9xjBsloaXkijB/BwHuF5i3 res9G4F+KCMOaGnbsobeXFjNwjLIFINLRHfQopsAyQpKbz2mC2wJ57a/5YHdFQXXUDHH hAM+iMADiNQH3iywrQ45viZSmk2ab/twwP5DI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

i've

 rpm -qa | grep -i xen-3
  xen-3.4.1_19718_05-1.1.x86_64

i'm trying to passthrough a PCI Eth NIC to a DomU

@ grub,

  module /vmlinuz-xen ... guestdev=0000:04:06.0 reassign_resources ...

and.

  test.cfg
        ...
        pci          = [ '04:06.0' ]
        ...

where,

lspci -vvv | grep -A20 04:06.0
        04:06.0 Ethernet controller: Intel Corporation 82541PI Gigabit
Ethernet Controller (rev 05)
                Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
                Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
                Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
                Interrupt: pin A routed to IRQ 20
                Region 0: Memory at fbf00000 (32-bit, non-prefetchable)
[disabled] [size=128K]
                Region 1: Memory at fbf20000 (32-bit, non-prefetchable)
[disabled] [size=128K]
                Region 2: I/O ports at ec00 [disabled] [size=64]
                Expansion ROM at f0180000 [disabled] [size=128K]
                Capabilities: [dc] Power Management version 2
                        Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                        Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
                Capabilities: [e4] PCI-X non-bridge device
                        Command: DPERE- ERO+ RBC=512 OST=1
                        Status: Dev=00:00.0 64bit- 133MHz- SCD- USC-
DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
                Kernel driver in use: pciback
        ...

@

 xm create -c test.cfg

I get,

        Error: pci: 0000:04:07.0 must be co-assigned to the same guest with
0000:04:06.0

fyi,

 lspci -vvv | grep -A20 04:07.0
        04:07.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X
Serial ATA Controller (rev 02)
                Subsystem: Silicon Image, Inc. Device 7124
                Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B- DisINTx-
                Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
                Interrupt: pin A routed to IRQ 21
                Region 0: Memory at fbf48000 (64-bit, non-prefetchable)
[disabled] [size=128]
                Region 2: Memory at fbf40000 (64-bit, non-prefetchable)
[disabled] [size=32K]
                Region 4: I/O ports at e880 [disabled] [size=16]
                Expansion ROM at f0100000 [disabled] [size=512K]
                Capabilities: [64] Power Management version 2
                        Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                        Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
                Capabilities: [40] PCI-X non-bridge device
                        Command: DPERE- ERO+ RBC=512 OST=12
                        Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC-
DC=simple DMMRBC=2048 DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz-
                Capabilities: [54] MSI: Enable- Count=1/1 Maskable- 64bit+
                        Address: 0000000000000000  Data: 0000
                Kernel driver in use: pciback


searching, i find a patch
(http://old.nabble.com/attachment/20011206/0/disable_co-assignment.patch)
@,

        
http://old.nabble.com/xen-3.3.0-pv-pci-passthrough-co-assigned-problem-td20008460.html

that doesn't make any difference.

i did find, @

        http://article.gmane.org/gmane.comp.emulators.xen.devel/72618
weidong.han <at> intel.com
        "I guess 07:00.0 and 07:00.1 are two PCI (non-PCIe) devices in your
system. PCI devices under the same bridge must be assigned to one
guest. Pls hide both of them by pci-stub, then you can assign both of
them to a guest, or just assign one
."

and,

        [Xen-devel] [PATCH] Xend: allow pci-stub to hide devices for assignment
    http://lists.xensource.com/archives/html/xen-devel/2009-07/msg00114.html

but, iiuc, pc-sub hiding is a pvops, not 'legacy' xen, capability ...

at this point, i'm unclear whether this is fixable :-/

Is the requirement to coassign PCI cards on the same bridge a *bug*
that's been fixed, or can be?

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


 


Rackspace

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