Carsten Schiers
2010-Apr-08 21:00 UTC
AW: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels
Hi, some short answers for now, it''s late here... - I will provide the compile log later - System has 4GB, DomU will recieve 256MB - forcedeth works on all kernels under Xen 3.4.1, never on Xen 4.0 - Mixing kernel versions will not help, it seems a problem between Xen 4.0 and the driver - All 2.6.3x kernels are pvops - I will try Pasi''s recomendation later this week Thanks & Best Regards, Carsten. ----- Originalnachricht ----- Von: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Gesendet: Don, 8.4.2010 22:46 An: Carsten Schiers <carsten@schiers.de> Cc: xen-devel <xen-devel@lists.xensource.com> ; jeremy <jeremy@goop.org> Betreff: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels On Thu, Apr 08, 2010 at 09:46:58PM +0200, Carsten Schiers wrote:> OK, I am still a bit fuzzy as I had to learn how to git and configure > kernels, and I am still unsure whether I did everything > right. Nevertheless, and even when I cannot provide a lot of details, I > would like to inform you about some anomalies. > > Currently, I run Xen 3.4.1 and 2.6.18.8 kernels, 64 Bit Dom0 and some 32 > Bit and 64 Bit DomUs on a Gigabyte M56S-S3 / AMD 4050e > with cpufreq on powernow-k8 in cpufreq=dom0-kernel mode. I make use of > PCI Passthrough for DVB-C cards and onboard NIC, as well > as for USB controller. > > > > Compile problem on xen/stable-2.6.32 > ------------------------------------ > > I compiled 2.6.32.10-pvops for DomU only mode, resulting in compile > error very similar to > > > http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00925.html > > I get a "static declaration of ''xen_register_gsi'' follows a non-static > declaration, because I have set CONFIG_XEN_PCI_MSI and > CONFIG_PCI_XEN, but not CONFIG_XEN_DOM0_PCI. It will disappear when > compiling a DOM0 kernel. >Can you do a copy-n-paste of your compile problem, please?> > > PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not > working on xen/stable-2.6.32 on Xen 3.4.1 > ------------------------------------------------------------------------ > --------------------------------------- > > It will allow passthrough of all mentioned devices except one of the PCI > controllers. It will not be detected. Using > xm pci-attach will produce an error: > > troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not > available because of BAR 0 [0xfc102000-0xfc1020ff] collisions > troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not > available because of BAR 0 [0xfc104000-0xfc104fff] collisionsHow much memory did you assign to the guest? If it is below 4GB, say 2GB did you see these errors?> nVidia forcedeth, working on pvops/Xen 3.4.1, not working on pvops/Xen > 4.0> ------------------------------------------------------------------------ > -- > > The whole experiment was done because when I use Xen 4.0 with my > 2.6.18.8 kernels, I cannot use the onboard NIC any longer. The > driver forcedeth will report an error. So, as using the pvops DomU on > Xen 3.4.1 worked, I tried to also use a pvops Dom0 underneathSo.. DomU and Dom0 with the same kernel works?> Xen 4.0, but the problem seems to be related to the Xen 4.0, which is > killing forcedeth MAC address detection. By the way: MSI has > never worked for me on that NIC. So I had pci=nomsi on kernel. > > not working example (MAC is random): > > troi kernel: [ 4.335591] forcedeth: Reverse Engineered nForce > ethernet driver. Version 0.64. > troi kernel: [ 4.335811] forcedeth 0000:00:00.0: enabling device > (0000 -> 0003) > troi kernel: [ 4.335942] forcedeth 0000:00:00.0: Xen PCI enabling > IRQ: 23 > troi kernel: [ 4.336016] forcedeth 0000:00:00.0: setting latency > timer to 64 > troi kernel: [ 4.336271] forcedeth 0000:00:00.0: Invalid Mac > address detected: 00:00:00:00:00:00 > troi kernel: [ 4.336295] forcedeth 0000:00:00.0: Please complain to > your hardware vendor. Switching to a random MAC. > troi kernel: [ 4.860537] forcedeth 0000:00:00.0: ifname eth0, PHY > OUI 0x732 @ 1, addr 5e:1a:09:69:77:5d > troi kernel: [ 4.860593] forcedeth 0000:00:00.0: highdma pwrctl > mgmt gbit lnktim msi desc-v3 > > working example (real MAC, note different IRQ): > > troi kernel: [ 1.133102] forcedeth: Reverse Engineered nForce > ethernet driver. Version 0.64. > troi kernel: [ 1.133376] forcedeth 0000:00:01.0: enabling device > (0000 -> 0003) > troi kernel: [ 1.133463] forcedeth 0000:00:01.0: Xen PCI enabling > IRQ: 19 > troi kernel: [ 1.652048] forcedeth 0000:00:01.0: ifname eth0, PHY > OUI 0x732 @ 1, addr 00:1d:7d:e8:97:7b > troi kernel: [ 1.652139] forcedeth 0000:00:01.0: highdma pwrctl > mgmt gbit lnktim msi desc-v3I got lost in your description. The failing case happens when your Dom0 is 2.6.18 or the 2.6.31 (or 2.6.32?) And is the DomU pv-ops or 2.6.18? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Carsten Schiers
2010-Apr-11 14:32 UTC
AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels
Hi, I am sorry to say that I mixed something. What does work now is 2.6.31.13 kernel. The error messages are gone now for 2.6.32.11, but it is still not functioning. So, with the 2.6.32.11 kernel, it will not recognize the same USB controller that is recognized by 2.6.31.13. When booting: [ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00 [ 0.325746] alloc irq_desc for 503 on node 0 [ 0.325753] alloc kstat_irqs on node 0 When I detach and attach from Dom0, it will log in the DomU: [ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 [ 202.848550] pcifront pci-0: backend going away! [ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses [ 202.903310] pcifront pci-0: 22 freeing event channel 9 [ 224.234600] pcifront pci-0: Installing PCI frontend [ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00 In Dom0 we have: ACPI: PCI interrupt for device 0000:00:02.1 disabled pciback: vpci: 0000:00:02.1: assign to virtual slot 0 For reference, the log entries when I detach/attach the device in 2.6.31.13: [ 47.250686] usb usb1: USB disconnect, address 1 [ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered [ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 [ 47.938006] pcifront pci-0: backend going away! [ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses [ 47.946981] pcifront pci-0: Device is in 6 state. Need to change state on the privileged domain. [ 47.952364] pcifront pci-0: Device is in 0 state. Need to change state on the privileged domain. [ 47.957636] pcifront pci-0: 22 freeing event channel 9 [ 58.832396] pcifront pci-0: Device is in 2 state. Need to change state on the privileged domain. [ 58.840387] pcifront pci-0: Device is in 3 state. Need to change state on the privileged domain. [ 58.868584] pcifront pci-0: Installing PCI frontend [ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00 [ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 0002) [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned bus number 1 [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 [ 59.497182] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 59.497194] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 59.497207] usb usb1: Product: EHCI Host Controller [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686 ehci_hcd [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 [ 59.497363] usb usb1: configuration #1 chosen from 1 choice [ 59.497447] hub 1-0:1.0: USB hub found [ 59.497643] hub 1-0:1.0: 10 ports detected Relevant XEN config entries in 2.6.32.11: CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=8 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y CONFIG_XEN_PCI_PASSTHROUGH=y CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_XEN_BLKDEV_FRONTEND=y CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=y CONFIG_XEN_KBDDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_FBDEV_FRONTEND=y CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=y CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y # CONFIG_XEN_GNTDEV is not set CONFIG_XEN_S3=y BR, Carsten. -----Ursprüngliche Nachricht----- Von: Carsten Schiers Gesendet: Samstag, 10. April 2010 11:27 An: ''Pasi Kärkkäinen'' Cc: ''xen-devel''; ''jeremy''; ''konrad.wilk'' Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Hi folks, some progress:>> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not>> working on xen/stable-2.6.32 on Xen 3.4.1 >>------------------------------------------------------------------------>> --------------------------------------- >> >> It will allow passthrough of all mentioned devices except one of thePCI>> controllers. It will not be detected. Using >> xm pci-attach will produce an error: >> >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions >> >> I first tried only with the 2nd function (or whatever it is called),but>> as you see, we have the same error with both put into >> the DomU. >> > >Have you seen this wiki page?: >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > >Try the "I get "non-page-aligned MMIO BAR" error when trying to startthe guest" thing.. maybe it helps? Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It works now with pvops 2.6.32.10 DomU kernel!!! Thanks Pasi!!! Eventually, you may put on the Wiki Page an example with more than one PCI device, so that hectic persons like me see better that a) it''s without parenthesis and b) a comma separated list ;o). BR, Carsten. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Carsten Schiers
2010-Apr-11 14:45 UTC
AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels
Two additional infos: here lspci of the two USB controllers. The 00:02.0
is passed into another DomU. I
should mention that I think the 00:02.0 is going down in case I pass
00:02.1 into the 2.6.32 domain, but
not if I pass it into the 2.6.31 domain. Find what the other DomU says
below.
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
(prog-if 10 [OHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 21
Region 0: Memory at c0200000 (32-bit, non-prefetchable)
[size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pciback
Kernel modules: ohci-hcd
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
(prog-if 20 [EHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin B routed to IRQ 20
Region 0: Memory at c0201000 (32-bit, non-prefetchable)
[disabled] [size=256]
Capabilities: [44] Debug port: BAR=1 offset=0098
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+
Kernel driver in use: pciback
Kernel modules: ehci-hcd
Apr 11 16:27:26 uhura kernel: fcusb: Rx URB status: -110
Apr 11 16:27:26 uhura kernel: usb 1-2: USB disconnect, address 3
Apr 11 16:27:26 uhura kernel: kcapi: card 1 down.
Apr 11 16:27:26 uhura kernel: kcapi: Controller 1: fcusb-0003
unregistered
Apr 11 16:27:26 uhura kernel: fcusb: Driver ''fcusb'' detached
Apr 11 16:27:26 uhura kernel: usb 1-2: new full speed USB device using
ohci_hcd and address 4
Apr 11 16:27:27 uhura kernel: usb 1-2: configuration #1 chosen from 1
choice
Apr 11 16:27:27 uhura kernel: fcusb: Driver ''fcusb'' attached
to stack.
(152)
Apr 11 16:27:27 uhura kernel: fcusb: Stack version 3.11-04
Apr 11 16:27:27 uhura kernel: kcapi: Controller 1: fcusb-0004 attached
Apr 11 16:27:27 uhura kernel: kcapi: card 1 "fcusb-0004" ready.
Apr 11 16:28:24 uhura kernel: fcusb: Rx URB status: -110
Apr 11 16:28:24 uhura kernel: usb 1-2: USB disconnect, address 4
Apr 11 16:28:25 uhura kernel: kcapi: card 1 down.
Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0004
unregistered
Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' detached
Apr 11 16:28:25 uhura kernel: usb 1-2: new full speed USB device using
ohci_hcd and address 5
Apr 11 16:28:25 uhura kernel: usb 1-2: configuration #1 chosen from 1
choice
Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' attached
to stack.
(152)
Apr 11 16:28:25 uhura kernel: fcusb: Stack version 3.11-04
Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0005 attached
Apr 11 16:28:25 uhura kernel: kcapi: card 1 "fcusb-0005" ready.
BR,
Carsten.
-----Ursprüngliche Nachricht-----
Von: Carsten Schiers
Gesendet: Sonntag, 11. April 2010 16:33
An: xen-devel
Cc: jeremy; konrad.wilk
Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /
2.6.32 pvops kernels
Hi,
I am sorry to say that I mixed something. What does work now is
2.6.31.13 kernel. The error
messages are gone now for 2.6.32.11, but it is still not functioning.
So, with the 2.6.32.11 kernel, it will not recognize the same USB
controller that is recognized
by 2.6.31.13.
When booting:
[ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00
[ 0.325746] alloc irq_desc for 503 on node 0
[ 0.325753] alloc kstat_irqs on node 0
When I detach and attach from Dom0, it will log in the DomU:
[ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00
[ 202.848550] pcifront pci-0: backend going away!
[ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses
[ 202.903310] pcifront pci-0: 22 freeing event channel 9
[ 224.234600] pcifront pci-0: Installing PCI frontend
[ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00
In Dom0 we have:
ACPI: PCI interrupt for device 0000:00:02.1 disabled
pciback: vpci: 0000:00:02.1: assign to virtual slot 0
For reference, the log entries when I detach/attach the device in
2.6.31.13:
[ 47.250686] usb usb1: USB disconnect, address 1
[ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered
[ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00
[ 47.938006] pcifront pci-0: backend going away!
[ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses
[ 47.946981] pcifront pci-0: Device is in 6 state. Need to change
state on the privileged domain.
[ 47.952364] pcifront pci-0: Device is in 0 state. Need to change
state on the privileged domain.
[ 47.957636] pcifront pci-0: 22 freeing event channel 9
[ 58.832396] pcifront pci-0: Device is in 2 state. Need to change
state on the privileged domain.
[ 58.840387] pcifront pci-0: Device is in 3 state. Need to change
state on the privileged domain.
[ 58.868584] pcifront pci-0: Installing PCI frontend
[ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00
[ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 0002)
[ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20
[ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20
[ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller
[ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned
bus number 1
[ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM
[ 59.491462] ehci_hcd 0000:00:00.1: debug port 1
[ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000
[ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00
[ 59.497182] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
[ 59.497194] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 59.497207] usb usb1: Product: EHCI Host Controller
[ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686
ehci_hcd
[ 59.497228] usb usb1: SerialNumber: 0000:00:00.1
[ 59.497363] usb usb1: configuration #1 chosen from 1 choice
[ 59.497447] hub 1-0:1.0: USB hub found
[ 59.497643] hub 1-0:1.0: 10 ports detected
Relevant XEN config entries in 2.6.32.11:
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=8
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_SWIOTLB_XEN=y
CONFIG_MICROCODE_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_DOM0_PCI=y
CONFIG_XEN_PCI_PASSTHROUGH=y
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_KBDDEV_FRONTEND=y
CONFIG_HVC_XEN=y
CONFIG_XEN_FBDEV_FRONTEND=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
# CONFIG_XEN_GNTDEV is not set
CONFIG_XEN_S3=y
BR,
Carsten.
-----Ursprüngliche Nachricht-----
Von: Carsten Schiers
Gesendet: Samstag, 10. April 2010 11:27
An: ''Pasi Kärkkäinen''
Cc: ''xen-devel''; ''jeremy'';
''konrad.wilk''
Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /
2.6.32 pvops kernels
Hi folks, some progress:
>> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not
>> working on xen/stable-2.6.32 on Xen 3.4.1
>>
------------------------------------------------------------------------>> ---------------------------------------
>>
>> It will allow passthrough of all mentioned devices except one of the
PCI >> controllers. It will not be detected. Using
>> xm pci-attach will produce an error:
>>
>> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not
>> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions
>> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not
>> available because of BAR 0 [0xfc104000-0xfc104fff] collisions
>>
>> I first tried only with the 2nd function (or whatever it is called),
but >> as you see, we have the same error with both put into
>> the DomU.
>>
>
>Have you seen this wiki page?:
>http://wiki.xensource.com/xenwiki/XenPCIpassthrough
>
>Try the "I get "non-page-aligned MMIO BAR" error when trying
to start
the guest" thing.. maybe it helps?
Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It
works now with pvops 2.6.32.10 DomU kernel!!!
Thanks Pasi!!!
Eventually, you may put on the Wiki Page an example with more than one
PCI device, so that hectic persons like
me see better that a) it''s without parenthesis and b) a comma separated
list ;o).
BR,
Carsten.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Carsten Schiers
2010-Apr-12 13:01 UTC
AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels
Yet another note: the kernel messages that break 00:02.0 come up when I use
2.6.31 kernel,
that means, if it is passing through the 00:02.1 into the pvops DomU, it will
break 00:02.0.
Please note that this will work with 2.6.18.8
BR,
Carsten.
----- Originalnachricht -----
Von: Carsten Schiers <carsten@schiers.de>
Gesendet: Son, 11.4.2010 16:45
An: xen-devel <xen-devel@lists.xensource.com>
Cc: jeremy <jeremy@goop.org> ; konrad.wilk <konrad.wilk@oracle.com>
Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32
pvops kernels
Two additional infos: here lspci of the two USB controllers. The 00:02.0 is
passed into another DomU. I
should mention that I think the 00:02.0 is going down in case I pass 00:02.1
into the 2.6.32 domain, but
not if I pass it into the 2.6.31 domain. Find what the other DomU says below.
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
(prog-if 10 [OHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 21
Region 0: Memory at c0200000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pciback
Kernel modules: ohci-hcd
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
(prog-if 20 [EHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin B routed to IRQ 20
Region 0: Memory at c0201000 (32-bit, non-prefetchable) [disabled]
[size=256]
Capabilities: [44] Debug port: BAR=1 offset=0098
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+
Kernel driver in use: pciback
Kernel modules: ehci-hcd
Apr 11 16:27:26 uhura kernel: fcusb: Rx URB status: -110
Apr 11 16:27:26 uhura kernel: usb 1-2: USB disconnect, address 3
Apr 11 16:27:26 uhura kernel: kcapi: card 1 down.
Apr 11 16:27:26 uhura kernel: kcapi: Controller 1: fcusb-0003 unregistered
Apr 11 16:27:26 uhura kernel: fcusb: Driver ''fcusb'' detached
Apr 11 16:27:26 uhura kernel: usb 1-2: new full speed USB device using ohci_hcd
and address 4
Apr 11 16:27:27 uhura kernel: usb 1-2: configuration #1 chosen from 1 choice
Apr 11 16:27:27 uhura kernel: fcusb: Driver ''fcusb'' attached
to stack. (152)
Apr 11 16:27:27 uhura kernel: fcusb: Stack version 3.11-04
Apr 11 16:27:27 uhura kernel: kcapi: Controller 1: fcusb-0004 attached
Apr 11 16:27:27 uhura kernel: kcapi: card 1 "fcusb-0004" ready.
Apr 11 16:28:24 uhura kernel: fcusb: Rx URB status: -110
Apr 11 16:28:24 uhura kernel: usb 1-2: USB disconnect, address 4
Apr 11 16:28:25 uhura kernel: kcapi: card 1 down.
Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0004 unregistered
Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' detached
Apr 11 16:28:25 uhura kernel: usb 1-2: new full speed USB device using ohci_hcd
and address 5
Apr 11 16:28:25 uhura kernel: usb 1-2: configuration #1 chosen from 1 choice
Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' attached
to stack. (152)
Apr 11 16:28:25 uhura kernel: fcusb: Stack version 3.11-04
Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0005 attached
Apr 11 16:28:25 uhura kernel: kcapi: card 1 "fcusb-0005" ready.
BR,
Carsten.
-----Ursprüngliche Nachricht-----
Von: Carsten Schiers
Gesendet: Sonntag, 11. April 2010 16:33
An: xen-devel
Cc: jeremy; konrad.wilk
Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32
pvops kernels
Hi,
I am sorry to say that I mixed something. What does work now is
2.6.31.13 kernel. The error
messages are gone now for 2.6.32.11, but it is still not functioning.
So, with the 2.6.32.11 kernel, it will not recognize the same USB
controller that is recognized
by 2.6.31.13.
When booting:
[ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00
[ 0.325746] alloc irq_desc for 503 on node 0
[ 0.325753] alloc kstat_irqs on node 0
When I detach and attach from Dom0, it will log in the DomU:
[ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00
[ 202.848550] pcifront pci-0: backend going away!
[ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses
[ 202.903310] pcifront pci-0: 22 freeing event channel 9
[ 224.234600] pcifront pci-0: Installing PCI frontend
[ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00
In Dom0 we have:
ACPI: PCI interrupt for device 0000:00:02.1 disabled
pciback: vpci: 0000:00:02.1: assign to virtual slot 0
For reference, the log entries when I detach/attach the device in
2.6.31.13:
[ 47.250686] usb usb1: USB disconnect, address 1
[ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered
[ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00
[ 47.938006] pcifront pci-0: backend going away!
[ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses
[ 47.946981] pcifront pci-0: Device is in 6 state. Need to change
state on the privileged domain.
[ 47.952364] pcifront pci-0: Device is in 0 state. Need to change
state on the privileged domain.
[ 47.957636] pcifront pci-0: 22 freeing event channel 9
[ 58.832396] pcifront pci-0: Device is in 2 state. Need to change
state on the privileged domain.
[ 58.840387] pcifront pci-0: Device is in 3 state. Need to change
state on the privileged domain.
[ 58.868584] pcifront pci-0: Installing PCI frontend
[ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00
[ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 0002)
[ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20
[ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20
[ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller
[ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned
bus number 1
[ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM
[ 59.491462] ehci_hcd 0000:00:00.1: debug port 1
[ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000
[ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00
[ 59.497182] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
[ 59.497194] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 59.497207] usb usb1: Product: EHCI Host Controller
[ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686
ehci_hcd
[ 59.497228] usb usb1: SerialNumber: 0000:00:00.1
[ 59.497363] usb usb1: configuration #1 chosen from 1 choice
[ 59.497447] hub 1-0:1.0: USB hub found
[ 59.497643] hub 1-0:1.0: 10 ports detected
Relevant XEN config entries in 2.6.32.11:
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=8
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_SWIOTLB_XEN=y
CONFIG_MICROCODE_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_DOM0_PCI=y
CONFIG_XEN_PCI_PASSTHROUGH=y
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_KBDDEV_FRONTEND=y
CONFIG_HVC_XEN=y
CONFIG_XEN_FBDEV_FRONTEND=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
# CONFIG_XEN_GNTDEV is not set
CONFIG_XEN_S3=y
BR,
Carsten.
-----Ursprüngliche Nachricht-----
Von: Carsten Schiers
Gesendet: Samstag, 10. April 2010 11:27
An: ''Pasi Kärkkäinen''
Cc: ''xen-devel''; ''jeremy'';
''konrad.wilk''
Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /
2.6.32 pvops kernels
Hi folks, some progress:
>> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not
>> working on xen/stable-2.6.32 on Xen 3.4.1
>>
------------------------------------------------------------------------>> ---------------------------------------
>>
>> It will allow passthrough of all mentioned devices except one of the
PCI >> controllers. It will not be detected. Using
>> xm pci-attach will produce an error:
>>
>> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not
>> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions
>> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not
>> available because of BAR 0 [0xfc104000-0xfc104fff] collisions
>>
>> I first tried only with the 2nd function (or whatever it is called),
but >> as you see, we have the same error with both put into
>> the DomU.
>>
>
>Have you seen this wiki page?:
>http://wiki.xensource.com/xenwiki/XenPCIpassthrough
>
>Try the "I get "non-page-aligned MMIO BAR" error when trying
to start
the guest" thing.. maybe it helps?
Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It
works now with pvops 2.6.32.10 DomU kernel!!!
Thanks Pasi!!!
Eventually, you may put on the Wiki Page an example with more than one
PCI device, so that hectic persons like
me see better that a) it''s without parenthesis and b) a comma separated
list ;o).
BR,
Carsten.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-12 13:07 UTC
Re: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels
On Mon, Apr 12, 2010 at 03:01:33PM +0200, Carsten Schiers wrote:> Yet another note: the kernel messages that break 00:02.0 come up when I use 2.6.31 kernel, > that means, if it is passing through the 00:02.1 into the pvops DomU, it will break 00:02.0. > > Please note that this will work with 2.6.18.8 >Maybe both of these devices need to be passed through at the same time to the same guest, since they''re part of the same device? -- Pasi> BR, > Carsten. > > ----- Originalnachricht ----- > Von: Carsten Schiers <carsten@schiers.de> > Gesendet: Son, 11.4.2010 16:45 > An: xen-devel <xen-devel@lists.xensource.com> > Cc: jeremy <jeremy@goop.org> ; konrad.wilk <konrad.wilk@oracle.com> > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels > > Two additional infos: here lspci of the two USB controllers. The 00:02.0 is passed into another DomU. I > should mention that I think the 00:02.0 is going down in case I pass 00:02.1 into the 2.6.32 domain, but > not if I pass it into the 2.6.31 domain. Find what the other DomU says below. > > 00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3) (prog-if 10 [OHCI]) > Subsystem: Giga-byte Technology Device 5004 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 (750ns min, 250ns max) > Interrupt: pin A routed to IRQ 21 > Region 0: Memory at c0200000 (32-bit, non-prefetchable) [size=4K] > Capabilities: [44] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: pciback > Kernel modules: ohci-hcd > > 00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3) (prog-if 20 [EHCI]) > Subsystem: Giga-byte Technology Device 5004 > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin B routed to IRQ 20 > Region 0: Memory at c0201000 (32-bit, non-prefetchable) [disabled] [size=256] > Capabilities: [44] Debug port: BAR=1 offset=0098 > Capabilities: [80] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME+ > Kernel driver in use: pciback > Kernel modules: ehci-hcd > > Apr 11 16:27:26 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:27:26 uhura kernel: usb 1-2: USB disconnect, address 3 > Apr 11 16:27:26 uhura kernel: kcapi: card 1 down. > Apr 11 16:27:26 uhura kernel: kcapi: Controller 1: fcusb-0003 unregistered > Apr 11 16:27:26 uhura kernel: fcusb: Driver ''fcusb'' detached > Apr 11 16:27:26 uhura kernel: usb 1-2: new full speed USB device using ohci_hcd and address 4 > Apr 11 16:27:27 uhura kernel: usb 1-2: configuration #1 chosen from 1 choice > Apr 11 16:27:27 uhura kernel: fcusb: Driver ''fcusb'' attached to stack. (152) > Apr 11 16:27:27 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:27:27 uhura kernel: kcapi: Controller 1: fcusb-0004 attached > Apr 11 16:27:27 uhura kernel: kcapi: card 1 "fcusb-0004" ready. > Apr 11 16:28:24 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:28:24 uhura kernel: usb 1-2: USB disconnect, address 4 > Apr 11 16:28:25 uhura kernel: kcapi: card 1 down. > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0004 unregistered > Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' detached > Apr 11 16:28:25 uhura kernel: usb 1-2: new full speed USB device using ohci_hcd and address 5 > Apr 11 16:28:25 uhura kernel: usb 1-2: configuration #1 chosen from 1 choice > Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' attached to stack. (152) > Apr 11 16:28:25 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0005 attached > Apr 11 16:28:25 uhura kernel: kcapi: card 1 "fcusb-0005" ready. > > BR, > Carsten. > > > -----Ursprüngliche Nachricht----- > Von: Carsten Schiers > Gesendet: Sonntag, 11. April 2010 16:33 > An: xen-devel > Cc: jeremy; konrad.wilk > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels > > Hi, > > I am sorry to say that I mixed something. What does work now is > 2.6.31.13 kernel. The error > messages are gone now for 2.6.32.11, but it is still not functioning. > > So, with the 2.6.32.11 kernel, it will not recognize the same USB > controller that is recognized > by 2.6.31.13. > > When booting: > > [ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 0.325746] alloc irq_desc for 503 on node 0 > [ 0.325753] alloc kstat_irqs on node 0 > > When I detach and attach from Dom0, it will log in the DomU: > > [ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 202.848550] pcifront pci-0: backend going away! > [ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 202.903310] pcifront pci-0: 22 freeing event channel 9 > [ 224.234600] pcifront pci-0: Installing PCI frontend > [ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > > In Dom0 we have: > > ACPI: PCI interrupt for device 0000:00:02.1 disabled > pciback: vpci: 0000:00:02.1: assign to virtual slot 0 > > For reference, the log entries when I detach/attach the device in > 2.6.31.13: > > [ 47.250686] usb usb1: USB disconnect, address 1 > [ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered > [ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 47.938006] pcifront pci-0: backend going away! > [ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 47.946981] pcifront pci-0: Device is in 6 state. Need to change > state on the privileged domain. > [ 47.952364] pcifront pci-0: Device is in 0 state. Need to change > state on the privileged domain. > [ 47.957636] pcifront pci-0: 22 freeing event channel 9 > [ 58.832396] pcifront pci-0: Device is in 2 state. Need to change > state on the privileged domain. > [ 58.840387] pcifront pci-0: Device is in 3 state. Need to change > state on the privileged domain. > [ 58.868584] pcifront pci-0: Installing PCI frontend > [ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 0002) > [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 > [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 > [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller > [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned > bus number 1 > [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM > [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 > [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 > [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 > [ 59.497182] usb usb1: New USB device found, idVendor=1d6b, > idProduct=0002 > [ 59.497194] usb usb1: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ 59.497207] usb usb1: Product: EHCI Host Controller > [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686 > ehci_hcd > [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 > [ 59.497363] usb usb1: configuration #1 chosen from 1 choice > [ 59.497447] hub 1-0:1.0: USB hub found > [ 59.497643] hub 1-0:1.0: 10 ports detected > > Relevant XEN config entries in 2.6.32.11: > > CONFIG_XEN=y > CONFIG_XEN_MAX_DOMAIN_MEMORY=8 > CONFIG_XEN_SAVE_RESTORE=y > # CONFIG_XEN_DEBUG_FS is not set > CONFIG_SWIOTLB_XEN=y > CONFIG_MICROCODE_XEN=y > CONFIG_XEN_DOM0=y > CONFIG_XEN_PRIVILEGED_GUEST=y > CONFIG_XEN_DOM0_PCI=y > CONFIG_XEN_PCI_PASSTHROUGH=y > CONFIG_PCI_XEN=y > CONFIG_XEN_PCIDEV_FRONTEND=y > CONFIG_XEN_BLKDEV_FRONTEND=y > CONFIG_NETXEN_NIC=m > CONFIG_XEN_NETDEV_FRONTEND=y > CONFIG_XEN_KBDDEV_FRONTEND=y > CONFIG_HVC_XEN=y > CONFIG_XEN_FBDEV_FRONTEND=y > CONFIG_XEN_BALLOON=y > CONFIG_XEN_SCRUB_PAGES=y > CONFIG_XEN_DEV_EVTCHN=y > CONFIG_XEN_BACKEND=y > CONFIG_XEN_NETDEV_BACKEND=y > CONFIG_XEN_BLKDEV_BACKEND=y > CONFIG_XEN_BLKDEV_TAP=y > CONFIG_XEN_BLKBACK_PAGEMAP=y > CONFIG_XEN_PCIDEV_BACKEND=y > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y > # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set > # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set > # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set > # CONFIG_XEN_PCIDEV_BE_DEBUG is not set > CONFIG_XENFS=y > CONFIG_XEN_COMPAT_XENFS=y > CONFIG_XEN_SYS_HYPERVISOR=y > CONFIG_XEN_XENBUS_FRONTEND=y > # CONFIG_XEN_GNTDEV is not set > CONFIG_XEN_S3=y > > BR, > Carsten. > > -----Ursprüngliche Nachricht----- > Von: Carsten Schiers > Gesendet: Samstag, 10. April 2010 11:27 > An: ''Pasi Kärkkäinen'' > Cc: ''xen-devel''; ''jeremy''; ''konrad.wilk'' > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / > 2.6.32 pvops kernels > > Hi folks, some progress: > > >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not > > >> working on xen/stable-2.6.32 on Xen 3.4.1 > >> > ------------------------------------------------------------------------ > >> --------------------------------------- > >> > >> It will allow passthrough of all mentioned devices except one of the > PCI > >> controllers. It will not be detected. Using > >> xm pci-attach will produce an error: > >> > >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not > >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions > >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not > >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions > >> > >> I first tried only with the 2nd function (or whatever it is called), > but > >> as you see, we have the same error with both put into > >> the DomU. > >> > > > >Have you seen this wiki page?: > >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start > the guest" thing.. maybe it helps? > > Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It > works now with pvops 2.6.32.10 DomU kernel!!! > > Thanks Pasi!!! > > Eventually, you may put on the Wiki Page an example with more than one > PCI device, so that hectic persons like > me see better that a) it''s without parenthesis and b) a comma separated > list ;o). > > BR, > Carsten. > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Carsten Schiers
2010-Apr-13 06:32 UTC
AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels
I thought so, too, but this doesn''t work either. And: it does work in 2.6.18, as I think it''s not realy two devices. One is OHCI, the other EHCI. BR, Carsten. ----- Originalnachricht ----- Von: Pasi Kärkkäinen <pasik@iki.fi> Gesendet: Mon, 12.4.2010 15:07 An: Carsten Schiers <carsten@schiers.de> Cc: jeremy <jeremy@goop.org> ; xen-devel <xen-devel@lists.xensource.com> ; konrad.wilk <konrad.wilk@oracle.com> Betreff: Re: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels On Mon, Apr 12, 2010 at 03:01:33PM +0200, Carsten Schiers wrote:> Yet another note: the kernel messages that break 00:02.0 come up when I use 2.6.31 kernel, > that means, if it is passing through the 00:02.1 into the pvops DomU, it will break 00:02.0. > > Please note that this will work with 2.6.18.8 >Maybe both of these devices need to be passed through at the same time to the same guest, since they''re part of the same device? -- Pasi> BR, > Carsten. > > ----- Originalnachricht ----- > Von: Carsten Schiers <carsten@schiers.de> > Gesendet: Son, 11.4.2010 16:45 > An: xen-devel <xen-devel@lists.xensource.com> > Cc: jeremy <jeremy@goop.org> ; konrad.wilk <konrad.wilk@oracle.com> > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels > > Two additional infos: here lspci of the two USB controllers. The 00:02.0 is passed into another DomU. I > should mention that I think the 00:02.0 is going down in case I pass 00:02.1 into the 2.6.32 domain, but > not if I pass it into the 2.6.31 domain. Find what the other DomU says below. > > 00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3) (prog-if 10 [OHCI]) > Subsystem: Giga-byte Technology Device 5004 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 (750ns min, 250ns max) > Interrupt: pin A routed to IRQ 21 > Region 0: Memory at c0200000 (32-bit, non-prefetchable) [size=4K] > Capabilities: [44] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: pciback > Kernel modules: ohci-hcd > > 00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3) (prog-if 20 [EHCI]) > Subsystem: Giga-byte Technology Device 5004 > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin B routed to IRQ 20 > Region 0: Memory at c0201000 (32-bit, non-prefetchable) [disabled] [size=256] > Capabilities: [44] Debug port: BAR=1 offset=0098 > Capabilities: [80] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME+ > Kernel driver in use: pciback > Kernel modules: ehci-hcd > > Apr 11 16:27:26 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:27:26 uhura kernel: usb 1-2: USB disconnect, address 3 > Apr 11 16:27:26 uhura kernel: kcapi: card 1 down. > Apr 11 16:27:26 uhura kernel: kcapi: Controller 1: fcusb-0003 unregistered > Apr 11 16:27:26 uhura kernel: fcusb: Driver ''fcusb'' detached > Apr 11 16:27:26 uhura kernel: usb 1-2: new full speed USB device using ohci_hcd and address 4 > Apr 11 16:27:27 uhura kernel: usb 1-2: configuration #1 chosen from 1 choice > Apr 11 16:27:27 uhura kernel: fcusb: Driver ''fcusb'' attached to stack. (152) > Apr 11 16:27:27 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:27:27 uhura kernel: kcapi: Controller 1: fcusb-0004 attached > Apr 11 16:27:27 uhura kernel: kcapi: card 1 "fcusb-0004" ready. > Apr 11 16:28:24 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:28:24 uhura kernel: usb 1-2: USB disconnect, address 4 > Apr 11 16:28:25 uhura kernel: kcapi: card 1 down. > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0004 unregistered > Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' detached > Apr 11 16:28:25 uhura kernel: usb 1-2: new full speed USB device using ohci_hcd and address 5 > Apr 11 16:28:25 uhura kernel: usb 1-2: configuration #1 chosen from 1 choice > Apr 11 16:28:25 uhura kernel: fcusb: Driver ''fcusb'' attached to stack. (152) > Apr 11 16:28:25 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0005 attached > Apr 11 16:28:25 uhura kernel: kcapi: card 1 "fcusb-0005" ready. > > BR, > Carsten. > > > -----Ursprüngliche Nachricht----- > Von: Carsten Schiers > Gesendet: Sonntag, 11. April 2010 16:33 > An: xen-devel > Cc: jeremy; konrad.wilk > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels > > Hi, > > I am sorry to say that I mixed something. What does work now is > 2.6.31.13 kernel. The error > messages are gone now for 2.6.32.11, but it is still not functioning. > > So, with the 2.6.32.11 kernel, it will not recognize the same USB > controller that is recognized > by 2.6.31.13. > > When booting: > > [ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 0.325746] alloc irq_desc for 503 on node 0 > [ 0.325753] alloc kstat_irqs on node 0 > > When I detach and attach from Dom0, it will log in the DomU: > > [ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 202.848550] pcifront pci-0: backend going away! > [ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 202.903310] pcifront pci-0: 22 freeing event channel 9 > [ 224.234600] pcifront pci-0: Installing PCI frontend > [ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > > In Dom0 we have: > > ACPI: PCI interrupt for device 0000:00:02.1 disabled > pciback: vpci: 0000:00:02.1: assign to virtual slot 0 > > For reference, the log entries when I detach/attach the device in > 2.6.31.13: > > [ 47.250686] usb usb1: USB disconnect, address 1 > [ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered > [ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 47.938006] pcifront pci-0: backend going away! > [ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 47.946981] pcifront pci-0: Device is in 6 state. Need to change > state on the privileged domain. > [ 47.952364] pcifront pci-0: Device is in 0 state. Need to change > state on the privileged domain. > [ 47.957636] pcifront pci-0: 22 freeing event channel 9 > [ 58.832396] pcifront pci-0: Device is in 2 state. Need to change > state on the privileged domain. > [ 58.840387] pcifront pci-0: Device is in 3 state. Need to change > state on the privileged domain. > [ 58.868584] pcifront pci-0: Installing PCI frontend > [ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 0002) > [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 > [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 > [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller > [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned > bus number 1 > [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM > [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 > [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 > [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 > [ 59.497182] usb usb1: New USB device found, idVendor=1d6b, > idProduct=0002 > [ 59.497194] usb usb1: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ 59.497207] usb usb1: Product: EHCI Host Controller > [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686 > ehci_hcd > [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 > [ 59.497363] usb usb1: configuration #1 chosen from 1 choice > [ 59.497447] hub 1-0:1.0: USB hub found > [ 59.497643] hub 1-0:1.0: 10 ports detected > > Relevant XEN config entries in 2.6.32.11: > > CONFIG_XEN=y > CONFIG_XEN_MAX_DOMAIN_MEMORY=8 > CONFIG_XEN_SAVE_RESTORE=y > # CONFIG_XEN_DEBUG_FS is not set > CONFIG_SWIOTLB_XEN=y > CONFIG_MICROCODE_XEN=y > CONFIG_XEN_DOM0=y > CONFIG_XEN_PRIVILEGED_GUEST=y > CONFIG_XEN_DOM0_PCI=y > CONFIG_XEN_PCI_PASSTHROUGH=y > CONFIG_PCI_XEN=y > CONFIG_XEN_PCIDEV_FRONTEND=y > CONFIG_XEN_BLKDEV_FRONTEND=y > CONFIG_NETXEN_NIC=m > CONFIG_XEN_NETDEV_FRONTEND=y > CONFIG_XEN_KBDDEV_FRONTEND=y > CONFIG_HVC_XEN=y > CONFIG_XEN_FBDEV_FRONTEND=y > CONFIG_XEN_BALLOON=y > CONFIG_XEN_SCRUB_PAGES=y > CONFIG_XEN_DEV_EVTCHN=y > CONFIG_XEN_BACKEND=y > CONFIG_XEN_NETDEV_BACKEND=y > CONFIG_XEN_BLKDEV_BACKEND=y > CONFIG_XEN_BLKDEV_TAP=y > CONFIG_XEN_BLKBACK_PAGEMAP=y > CONFIG_XEN_PCIDEV_BACKEND=y > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y > # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set > # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set > # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set > # CONFIG_XEN_PCIDEV_BE_DEBUG is not set > CONFIG_XENFS=y > CONFIG_XEN_COMPAT_XENFS=y > CONFIG_XEN_SYS_HYPERVISOR=y > CONFIG_XEN_XENBUS_FRONTEND=y > # CONFIG_XEN_GNTDEV is not set > CONFIG_XEN_S3=y > > BR, > Carsten. > > -----Ursprüngliche Nachricht----- > Von: Carsten Schiers > Gesendet: Samstag, 10. April 2010 11:27 > An: ''Pasi Kärkkäinen'' > Cc: ''xen-devel''; ''jeremy''; ''konrad.wilk'' > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / > 2.6.32 pvops kernels > > Hi folks, some progress: > > >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not > > >> working on xen/stable-2.6.32 on Xen 3.4.1 > >> > ------------------------------------------------------------------------ > >> --------------------------------------- > >> > >> It will allow passthrough of all mentioned devices except one of the > PCI > >> controllers. It will not be detected. Using > >> xm pci-attach will produce an error: > >> > >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not > >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions > >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not > >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions > >> > >> I first tried only with the 2nd function (or whatever it is called), > but > >> as you see, we have the same error with both put into > >> the DomU. > >> > > > >Have you seen this wiki page?: > >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start > the guest" thing.. maybe it helps? > > Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It > works now with pvops 2.6.32.10 DomU kernel!!! > > Thanks Pasi!!! > > Eventually, you may put on the Wiki Page an example with more than one > PCI device, so that hectic persons like > me see better that a) it''s without parenthesis and b) a comma separated > list ;o). > > BR, > Carsten. > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel