francisco javier funes nieto
2009-Dec-09 17:13 UTC
[Xen-users] Problems with pci passthrough with Xen 3.4.2
Hi all!. First of all sorry about my English it''s not very fluid. I have a small server based upon Supermicro X7DBN (Chipset Intel® 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM RAM. The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny in domU (2.6.26-2-xen-amd64). Xen is 3.4.2 compiled from sources. The problem comes when I need to passthrough the second gigabit ethernet interface to a domU. I''ve got an "pci: improper device assignment specified:" error. Here is the menu.lst: module /boot/vmlinuz-2.6.26-2-xen-amd64 root=/dev/sda1 ro console=tty0 pci=nomsi pciback.hide=(04:00.1) Here is the lspci output: main:~# lspci |grep Ethernet 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01) 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01) Here''s the xm info: main:~# xm info host : main.chauchinasincables.es release : 2.6.26-2-xen-amd64 version : #1 SMP Thu Nov 5 04:27:12 UTC 2009 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 1866 hw_caps : bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 4094 free_memory : 128 node_to_cpu : node0:0-3 node_to_memory : node0:128 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : chauchinasincables.es cc_compile_date : Tue Dec 8 20:57:01 CET 2009 xend_config_format : 4 Here''s the domU config file with pci device: pci = [''04:00.1''] And here''s the error when I try to create the VM: main:~# xm create /etc/xen/proxy.chauchinasincables.es.cfg Using config file "/etc/xen/proxy.chauchinasincables.es.cfg". Error: pci: improper device assignment specified: pci: 0000:04:00.0 must be co-assigned to the same guest with 0000:04:00.1, but it is not owned by pciback. With Xen from Debian Repository (3.2-1) it works very well! But not the same result with compiled from source Xen (3.4.2). Can anyone show me how to configure this? I''ve tried xm pci-attach but pci-list-assignable-devices shows nothing and pciback module show that the device is seized from dom0. I''m really lost... thanks in advance. -- _____________________________________________ Francisco Javier Funes Nieto [esencia@gmail.com] CANONIGOS Servicios Informáticos para PYMES. Cl. Cruz 2, 1º Oficina 7 Tlf: 958.536759 / 661134556 Fax: 958.521354 GRANADA - 18002 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stefan Kuhne
2009-Dec-09 17:48 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
francisco javier funes nieto schrieb: Hi,> main:~# xm create /etc/xen/proxy.chauchinasincables.es.cfg > Using config file "/etc/xen/proxy.chauchinasincables.es.cfg". > Error: pci: improper device assignment specified: pci: 0000:04:00.0 > must be co-assigned to the same guest with 0000:04:00.1, but it is not > owned by pciback. >google for "FLR Patch" should help. Stefan Kuhne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2009-Dec-09 18:37 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
On Wed, Dec 09, 2009 at 06:13:14PM +0100, francisco javier funes nieto wrote:> Hi all!. > > First of all sorry about my English it''s not very fluid. > > I have a small server based upon Supermicro X7DBN (Chipset Intel® > 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM > RAM. > > The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny > in domU (2.6.26-2-xen-amd64). >You might want to try the latest ''official'' Xen 3.4.x dom0 kernel: http://xenbits.xen.org/linux-2.6.18-xen.hg I know someone who got pci-passthrough working with Xen 3.4.2 and 2.6.18-xen dom0 kernel.> Xen is 3.4.2 compiled from sources. > > The problem comes when I need to passthrough the second gigabit > ethernet interface to a domU. I''ve got an "pci: improper device > assignment specified:" error. > > Here is the menu.lst: > > module /boot/vmlinuz-2.6.26-2-xen-amd64 root=/dev/sda1 ro > console=tty0 pci=nomsi pciback.hide=(04:00.1) > > > Here is the lspci output: > > main:~# lspci |grep Ethernet > > 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) > 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) >So this is a so called multi-function device? I think you should hide both the functions from dom0!> Here''s the xm info: > > main:~# xm info > host : main.chauchinasincables.es > release : 2.6.26-2-xen-amd64 > version : #1 SMP Thu Nov 5 04:27:12 UTC 2009 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 1866 > hw_caps : > bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 4094 > free_memory : 128 > node_to_cpu : node0:0-3 > node_to_memory : node0:128 > xen_major : 3 > xen_minor : 4 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > cc_compile_by : root > cc_compile_domain : chauchinasincables.es > cc_compile_date : Tue Dec 8 20:57:01 CET 2009 > xend_config_format : 4 > > Here''s the domU config file with pci device: > > pci = [''04:00.1''] > > > > And here''s the error when I try to create the VM: > > main:~# xm create /etc/xen/proxy.chauchinasincables.es.cfg > Using config file "/etc/xen/proxy.chauchinasincables.es.cfg". > Error: pci: improper device assignment specified: pci: 0000:04:00.0 > must be co-assigned to the same guest with 0000:04:00.1, but it is not > owned by pciback. >There it is.. you have to passthrough _both_ of the functions at the same time.> > With Xen from Debian Repository (3.2-1) it works very well! > But not the same result with compiled from source Xen (3.4.2). > > Can anyone show me how to configure this? > > I''ve tried xm pci-attach but pci-list-assignable-devices shows nothing > and pciback module show that the device is seized from dom0. > > I''m really lost... > > thanks in advance. >Try passing both of the PCI ids, and see if it works then. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
francisco javier funes nieto
2009-Dec-09 18:41 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
Thank''s Stefan but I''ve not found a diff path to apply the source code of Xen... I''ll do a deep search, thank''s again. Pasi, the two lines in lspci are the two gigabit ethernet interfaces built in the mainboard, when I hide them the dom0 gets no ethernet link. (eth0 not found) Maybe I need to buy an simple pci-ethernet-gigabit and asign it to the domU? J. 2009/12/9 Pasi Kärkkäinen <pasik@iki.fi>:> On Wed, Dec 09, 2009 at 06:13:14PM +0100, francisco javier funes nieto wrote: >> Hi all!. >> >> First of all sorry about my English it''s not very fluid. >> >> I have a small server based upon Supermicro X7DBN (Chipset Intel® >> 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM >> RAM. >> >> The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny >> in domU (2.6.26-2-xen-amd64). >> > > You might want to try the latest ''official'' Xen 3.4.x dom0 kernel: > http://xenbits.xen.org/linux-2.6.18-xen.hg > > I know someone who got pci-passthrough working with Xen 3.4.2 and > 2.6.18-xen dom0 kernel. > > >> Xen is 3.4.2 compiled from sources. >> >> The problem comes when I need to passthrough the second gigabit >> ethernet interface to a domU. I''ve got an "pci: improper device >> assignment specified:" error. >> >> Here is the menu.lst: >> >> module /boot/vmlinuz-2.6.26-2-xen-amd64 root=/dev/sda1 ro >> console=tty0 pci=nomsi pciback.hide=(04:00.1) >> >> >> Here is the lspci output: >> >> main:~# lspci |grep Ethernet >> >> 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit >> Ethernet Controller (Copper) (rev 01) >> 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit >> Ethernet Controller (Copper) (rev 01) >> > > > So this is a so called multi-function device? > I think you should hide both the functions from dom0! > > >> Here''s the xm info: >> >> main:~# xm info >> host : main.chauchinasincables.es >> release : 2.6.26-2-xen-amd64 >> version : #1 SMP Thu Nov 5 04:27:12 UTC 2009 >> machine : x86_64 >> nr_cpus : 4 >> nr_nodes : 1 >> cores_per_socket : 4 >> threads_per_core : 1 >> cpu_mhz : 1866 >> hw_caps : >> bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001:00000000 >> virt_caps : hvm >> total_memory : 4094 >> free_memory : 128 >> node_to_cpu : node0:0-3 >> node_to_memory : node0:128 >> xen_major : 3 >> xen_minor : 4 >> xen_extra : .2 >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> xen_scheduler : credit >> xen_pagesize : 4096 >> platform_params : virt_start=0xffff800000000000 >> xen_changeset : unavailable >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >> cc_compile_by : root >> cc_compile_domain : chauchinasincables.es >> cc_compile_date : Tue Dec 8 20:57:01 CET 2009 >> xend_config_format : 4 >> >> Here''s the domU config file with pci device: >> >> pci = [''04:00.1''] >> >> >> >> And here''s the error when I try to create the VM: >> >> main:~# xm create /etc/xen/proxy.chauchinasincables.es.cfg >> Using config file "/etc/xen/proxy.chauchinasincables.es.cfg". >> Error: pci: improper device assignment specified: pci: 0000:04:00.0 >> must be co-assigned to the same guest with 0000:04:00.1, but it is not >> owned by pciback. >> > > There it is.. you have to passthrough _both_ of the functions at the > same time. > >> >> With Xen from Debian Repository (3.2-1) it works very well! >> But not the same result with compiled from source Xen (3.4.2). >> >> Can anyone show me how to configure this? >> >> I''ve tried xm pci-attach but pci-list-assignable-devices shows nothing >> and pciback module show that the device is seized from dom0. >> >> I''m really lost... >> >> thanks in advance. >> > > Try passing both of the PCI ids, and see if it works then. > > -- Pasi > >-- _____________________________________________ Francisco Javier Funes Nieto [esencia@gmail.com] CANONIGOS Servicios Informáticos para PYMES. Cl. Cruz 2, 1º Oficina 7 Tlf: 958.536759 / 661134556 Fax: 958.521354 GRANADA - 18002 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2009-Dec-09 18:59 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
On Wed, Dec 09, 2009 at 07:41:46PM +0100, francisco javier funes nieto wrote:> Thank''s Stefan but I''ve not found a diff path to apply the source code > of Xen... I''ll do a deep search, thank''s again. > > Pasi, the two lines in lspci are the two gigabit ethernet interfaces > built in the mainboard, when I hide them the dom0 gets no ethernet > link. (eth0 not found) >Ok.. were you able to successfully passthrough only other port with earlier Xen version? I think Xen 3.4.2 added some "multi-function" device passthrough patches.. but I guess that shouldn''t require you to passthrough all the functions at the same time. Dunno. I haven''t really used it myself.> Maybe I need to buy an simple pci-ethernet-gigabit and asign it to the domU? >That works at least. -- Pasi> J. > > 2009/12/9 Pasi Kärkkäinen <pasik@iki.fi>: > > On Wed, Dec 09, 2009 at 06:13:14PM +0100, francisco javier funes nieto wrote: > >> Hi all!. > >> > >> First of all sorry about my English it''s not very fluid. > >> > >> I have a small server based upon Supermicro X7DBN (Chipset Intel® > >> 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM > >> RAM. > >> > >> The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny > >> in domU (2.6.26-2-xen-amd64). > >> > > > > You might want to try the latest ''official'' Xen 3.4.x dom0 kernel: > > http://xenbits.xen.org/linux-2.6.18-xen.hg > > > > I know someone who got pci-passthrough working with Xen 3.4.2 and > > 2.6.18-xen dom0 kernel. > > > > > >> Xen is 3.4.2 compiled from sources. > >> > >> The problem comes when I need to passthrough the second gigabit > >> ethernet interface to a domU. I''ve got an "pci: improper device > >> assignment specified:" error. > >> > >> Here is the menu.lst: > >> > >> module /boot/vmlinuz-2.6.26-2-xen-amd64 root=/dev/sda1 ro > >> console=tty0 pci=nomsi pciback.hide=(04:00.1) > >> > >> > >> Here is the lspci output: > >> > >> main:~# lspci |grep Ethernet > >> > >> 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > >> Ethernet Controller (Copper) (rev 01) > >> 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > >> Ethernet Controller (Copper) (rev 01) > >> > > > > > > So this is a so called multi-function device? > > I think you should hide both the functions from dom0! > > > > > >> Here''s the xm info: > >> > >> main:~# xm info > >> host : main.chauchinasincables.es > >> release : 2.6.26-2-xen-amd64 > >> version : #1 SMP Thu Nov 5 04:27:12 UTC 2009 > >> machine : x86_64 > >> nr_cpus : 4 > >> nr_nodes : 1 > >> cores_per_socket : 4 > >> threads_per_core : 1 > >> cpu_mhz : 1866 > >> hw_caps : > >> bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001:00000000 > >> virt_caps : hvm > >> total_memory : 4094 > >> free_memory : 128 > >> node_to_cpu : node0:0-3 > >> node_to_memory : node0:128 > >> xen_major : 3 > >> xen_minor : 4 > >> xen_extra : .2 > >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > >> hvm-3.0-x86_32p hvm-3.0-x86_64 > >> xen_scheduler : credit > >> xen_pagesize : 4096 > >> platform_params : virt_start=0xffff800000000000 > >> xen_changeset : unavailable > >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > >> cc_compile_by : root > >> cc_compile_domain : chauchinasincables.es > >> cc_compile_date : Tue Dec 8 20:57:01 CET 2009 > >> xend_config_format : 4 > >> > >> Here''s the domU config file with pci device: > >> > >> pci = [''04:00.1''] > >> > >> > >> > >> And here''s the error when I try to create the VM: > >> > >> main:~# xm create /etc/xen/proxy.chauchinasincables.es.cfg > >> Using config file "/etc/xen/proxy.chauchinasincables.es.cfg". > >> Error: pci: improper device assignment specified: pci: 0000:04:00.0 > >> must be co-assigned to the same guest with 0000:04:00.1, but it is not > >> owned by pciback. > >> > > > > There it is.. you have to passthrough _both_ of the functions at the > > same time. > > > >> > >> With Xen from Debian Repository (3.2-1) it works very well! > >> But not the same result with compiled from source Xen (3.4.2). > >> > >> Can anyone show me how to configure this? > >> > >> I''ve tried xm pci-attach but pci-list-assignable-devices shows nothing > >> and pciback module show that the device is seized from dom0. > >> > >> I''m really lost... > >> > >> thanks in advance. > >> > > > > Try passing both of the PCI ids, and see if it works then. > > > > -- Pasi > > > > > > > > -- > _____________________________________________ > > Francisco Javier Funes Nieto [esencia@gmail.com] > CANONIGOS > Servicios Informáticos para PYMES. > Cl. Cruz 2, 1º Oficina 7 > Tlf: 958.536759 / 661134556 > Fax: 958.521354 > GRANADA - 18002_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stefan Kuhne
2009-Dec-09 21:10 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
francisco javier funes nieto schrieb:> Thank''s Stefan but I''ve not found a diff path to apply the source code > of Xen... I''ll do a deep search, thank''s again. >I''ve found it in my archiv: http://old.nabble.com/Error:-pci:-0000:02:06.0-must-be-co-assigned-to-the-same-guest-with-0000:02:05.0-td21280150.html Stefan Kuhne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
francisco javier funes nieto
2009-Dec-14 11:30 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
Thanks to all, it works like a charm. Now I have the Ethernet device in the DomU, once I patched the Xen Source Tree and recompile with the FLR patch. Great! Really Great! Javier 2009/12/9 Stefan Kuhne <stefan.kuhne@gmx.net>:> francisco javier funes nieto schrieb: >> Thank''s Stefan but I''ve not found a diff path to apply the source code >> of Xen... I''ll do a deep search, thank''s again. >> > I''ve found it in my archiv: > http://old.nabble.com/Error:-pci:-0000:02:06.0-must-be-co-assigned-to-the-same-guest-with-0000:02:05.0-td21280150.html > > Stefan Kuhne > >-- _____________________________________________ Francisco Javier Funes Nieto [esencia@gmail.com] CANONIGOS Servicios Informáticos para PYMES. Cl. Cruz 2, 1º Oficina 7 Tlf: 958.536759 / 661134556 Fax: 958.521354 GRANADA - 18002 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2009-Dec-14 11:58 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
On Mon, Dec 14, 2009 at 12:30:09PM +0100, francisco javier funes nieto wrote:> Thanks to all, it works like a charm. > > Now I have the Ethernet device in the DomU, once I patched the Xen > Source Tree and recompile with the FLR patch. > > Great! > > Really Great! >Hello. Just to confirm, with the FLR patch, you''re able to use the first port in dom0, and passthrough the second port to domU? Thanks! -- Pasi> Javier > > 2009/12/9 Stefan Kuhne <stefan.kuhne@gmx.net>: > > francisco javier funes nieto schrieb: > >> Thank''s Stefan but I''ve not found a diff path to apply the source code > >> of Xen... I''ll do a deep search, thank''s again. > >> > > I''ve found it in my archiv: > > http://old.nabble.com/Error:-pci:-0000:02:06.0-must-be-co-assigned-to-the-same-guest-with-0000:02:05.0-td21280150.html > > > > Stefan Kuhne > > > > > > > > -- > _____________________________________________ > > Francisco Javier Funes Nieto [esencia@gmail.com] > CANONIGOS > Servicios Informáticos para PYMES. > Cl. Cruz 2, 1º Oficina 7 > Tlf: 958.536759 / 661134556 > Fax: 958.521354 > GRANADA - 18002 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
francisco javier funes nieto
2009-Dec-14 12:06 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
Yes! This is the lspci output from dom0: main:/etc/xen# lspci |grep Ethernet 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01) 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01) And the lspci from domU: proxy:~# lspci -v 00:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01) Subsystem: Super Micro Computer Inc Device 0000 Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at da020000 (32-bit, non-prefetchable) [size=128K] I/O ports at 3020 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting <?> Capabilities: [140] Device Serial Number 22-6c-32-ff-ff-48-30-00 Kernel driver in use: e1000e Kernel modules: e1000e>From this moment I''m still working in this domU to use this Ethernetpassed by passthrough as primary interface for the Squid Proxy. The dom0 works as expected! I''ll put iperf results as soon I configure the Squid. Thanks! J. 2009/12/14 Pasi Kärkkäinen <pasik@iki.fi>:> On Mon, Dec 14, 2009 at 12:30:09PM +0100, francisco javier funes nieto wrote: >> Thanks to all, it works like a charm. >> >> Now I have the Ethernet device in the DomU, once I patched the Xen >> Source Tree and recompile with the FLR patch. >> >> Great! >> >> Really Great! >> > > Hello. > > Just to confirm, with the FLR patch, you''re able to use the first port > in dom0, and passthrough the second port to domU? > > Thanks! > > -- Pasi > >> Javier >> >> 2009/12/9 Stefan Kuhne <stefan.kuhne@gmx.net>: >> > francisco javier funes nieto schrieb: >> >> Thank''s Stefan but I''ve not found a diff path to apply the source code >> >> of Xen... I''ll do a deep search, thank''s again. >> >> >> > I''ve found it in my archiv: >> > http://old.nabble.com/Error:-pci:-0000:02:06.0-must-be-co-assigned-to-the-same-guest-with-0000:02:05.0-td21280150.html >> > >> > Stefan Kuhne >> > >> > >> >> >> >> -- >> _____________________________________________ >> >> Francisco Javier Funes Nieto [esencia@gmail.com] >> CANONIGOS >> Servicios Informáticos para PYMES. >> Cl. Cruz 2, 1º Oficina 7 >> Tlf: 958.536759 / 661134556 >> Fax: 958.521354 >> GRANADA - 18002 >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >-- _____________________________________________ Francisco Javier Funes Nieto [esencia@gmail.com] CANONIGOS Servicios Informáticos para PYMES. Cl. Cruz 2, 1º Oficina 7 Tlf: 958.536759 / 661134556 Fax: 958.521354 GRANADA - 18002 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
francisco javier funes nieto
2009-Dec-14 12:30 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
The domU acting as iPerf Server. proxy:~# iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.2.246 port 5001 connected with 192.168.2.49 port 65339 [ 4] 0.0-60.0 sec 6.53 GBytes 934 Mbits/sec The domU acting as iPerf Client. proxy:~# iperf -c 192.168.2.49 -t 60 ------------------------------------------------------------ Client connecting to 192.168.2.49, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.2.246 port 52712 connected with 192.168.2.49 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-60.0 sec 6.58 GBytes 941 Mbits/sec That''s all folks.. Thanks again ;) 2009/12/14 francisco javier funes nieto <esencia@gmail.com>:> Yes! > > This is the lspci output from dom0: > > main:/etc/xen# lspci |grep Ethernet > 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) > 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) > > > And the lspci from domU: > > proxy:~# lspci -v > 00:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) > Subsystem: Super Micro Computer Inc Device 0000 > Flags: bus master, fast devsel, latency 0, IRQ 19 > Memory at da020000 (32-bit, non-prefetchable) [size=128K] > I/O ports at 3020 [size=32] > Capabilities: [c8] Power Management version 2 > Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- > Capabilities: [e0] Express Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting <?> > Capabilities: [140] Device Serial Number 22-6c-32-ff-ff-48-30-00 > Kernel driver in use: e1000e > Kernel modules: e1000e > > From this moment I''m still working in this domU to use this Ethernet > passed by passthrough as primary interface for the Squid Proxy. > > The dom0 works as expected! > > > I''ll put iperf results as soon I configure the Squid. > > > Thanks! > > J. > > > > 2009/12/14 Pasi Kärkkäinen <pasik@iki.fi>: >> On Mon, Dec 14, 2009 at 12:30:09PM +0100, francisco javier funes nieto wrote: >>> Thanks to all, it works like a charm. >>> >>> Now I have the Ethernet device in the DomU, once I patched the Xen >>> Source Tree and recompile with the FLR patch. >>> >>> Great! >>> >>> Really Great! >>> >> >> Hello. >> >> Just to confirm, with the FLR patch, you''re able to use the first port >> in dom0, and passthrough the second port to domU? >> >> Thanks! >> >> -- Pasi >> >>> Javier >>> >>> 2009/12/9 Stefan Kuhne <stefan.kuhne@gmx.net>: >>> > francisco javier funes nieto schrieb: >>> >> Thank''s Stefan but I''ve not found a diff path to apply the source code >>> >> of Xen... I''ll do a deep search, thank''s again. >>> >> >>> > I''ve found it in my archiv: >>> > http://old.nabble.com/Error:-pci:-0000:02:06.0-must-be-co-assigned-to-the-same-guest-with-0000:02:05.0-td21280150.html >>> > >>> > Stefan Kuhne >>> > >>> > >>> >>> >>> >>> -- >>> _____________________________________________ >>> >>> Francisco Javier Funes Nieto [esencia@gmail.com] >>> CANONIGOS >>> Servicios Informáticos para PYMES. >>> Cl. Cruz 2, 1º Oficina 7 >>> Tlf: 958.536759 / 661134556 >>> Fax: 958.521354 >>> GRANADA - 18002 >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >> > > > > -- > _____________________________________________ > > Francisco Javier Funes Nieto [esencia@gmail.com] > CANONIGOS > Servicios Informáticos para PYMES. > Cl. Cruz 2, 1º Oficina 7 > Tlf: 958.536759 / 661134556 > Fax: 958.521354 > GRANADA - 18002 >-- _____________________________________________ Francisco Javier Funes Nieto [esencia@gmail.com] CANONIGOS Servicios Informáticos para PYMES. Cl. Cruz 2, 1º Oficina 7 Tlf: 958.536759 / 661134556 Fax: 958.521354 GRANADA - 18002 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2009-Dec-14 12:31 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
On Mon, Dec 14, 2009 at 01:30:22PM +0100, francisco javier funes nieto wrote:> The domU acting as iPerf Server. > > proxy:~# iperf -s > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 85.3 KByte (default) > ------------------------------------------------------------ > [ 4] local 192.168.2.246 port 5001 connected with 192.168.2.49 port 65339 > [ 4] 0.0-60.0 sec 6.53 GBytes 934 Mbits/sec > > > The domU acting as iPerf Client. > > proxy:~# iperf -c 192.168.2.49 -t 60 > ------------------------------------------------------------ > Client connecting to 192.168.2.49, TCP port 5001 > TCP window size: 16.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 192.168.2.246 port 52712 connected with 192.168.2.49 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-60.0 sec 6.58 GBytes 941 Mbits/sec > > > That''s all folks.. > > Thanks again ;) >Nice. Seems to work very well. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2009-Dec-14 14:08 UTC
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
On Mon, Dec 14, 2009 at 01:06:10PM +0100, francisco javier funes nieto wrote:> Yes! > > This is the lspci output from dom0: > > main:/etc/xen# lspci |grep Ethernet > 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) > 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) > > > And the lspci from domU: > > proxy:~# lspci -v > 00:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit > Ethernet Controller (Copper) (rev 01) > Subsystem: Super Micro Computer Inc Device 0000 > Flags: bus master, fast devsel, latency 0, IRQ 19 > Memory at da020000 (32-bit, non-prefetchable) [size=128K] > I/O ports at 3020 [size=32] > Capabilities: [c8] Power Management version 2 > Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- > Capabilities: [e0] Express Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting <?> > Capabilities: [140] Device Serial Number 22-6c-32-ff-ff-48-30-00 > Kernel driver in use: e1000e > Kernel modules: e1000e > > From this moment I''m still working in this domU to use this Ethernet > passed by passthrough as primary interface for the Squid Proxy. > > The dom0 works as expected! >Btw current xen-unstable (upcoming Xen 4.0) doesn''t need the "disable FLR" patch, it has an option you can use to overcome this: http://lists.xensource.com/archives/html/xen-devel/2009-12/msg00682.html "Actually we have such a xend option in the xen-unstable tree: The option is at the end of /etc/xen/xend-config.sxp: (pci-passthrough-strict-check yes). Uncomment it and change it to no and do a "xend restart". -- Pasi> > I''ll put iperf results as soon I configure the Squid. > > > Thanks! > > J. > > > > 2009/12/14 Pasi Kärkkäinen <pasik@iki.fi>: > > On Mon, Dec 14, 2009 at 12:30:09PM +0100, francisco javier funes nieto wrote: > >> Thanks to all, it works like a charm. > >> > >> Now I have the Ethernet device in the DomU, once I patched the Xen > >> Source Tree and recompile with the FLR patch. > >> > >> Great! > >> > >> Really Great! > >> > > > > Hello. > > > > Just to confirm, with the FLR patch, you''re able to use the first port > > in dom0, and passthrough the second port to domU? > > > > Thanks! > > > > -- Pasi > > > >> Javier > >> > >> 2009/12/9 Stefan Kuhne <stefan.kuhne@gmx.net>: > >> > francisco javier funes nieto schrieb: > >> >> Thank''s Stefan but I''ve not found a diff path to apply the source code > >> >> of Xen... I''ll do a deep search, thank''s again. > >> >> > >> > I''ve found it in my archiv: > >> > http://old.nabble.com/Error:-pci:-0000:02:06.0-must-be-co-assigned-to-the-same-guest-with-0000:02:05.0-td21280150.html > >> > > >> > Stefan Kuhne > >> > > >> > > >> > >> > >> > >> -- > >> _____________________________________________ > >> > >> Francisco Javier Funes Nieto [esencia@gmail.com] > >> CANONIGOS > >> Servicios Informáticos para PYMES. > >> Cl. Cruz 2, 1º Oficina 7 > >> Tlf: 958.536759 / 661134556 > >> Fax: 958.521354 > >> GRANADA - 18002 > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > > > > > > -- > _____________________________________________ > > Francisco Javier Funes Nieto [esencia@gmail.com] > CANONIGOS > Servicios Informáticos para PYMES. > Cl. Cruz 2, 1º Oficina 7 > Tlf: 958.536759 / 661134556 > Fax: 958.521354 > GRANADA - 18002_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users