Christopher R. K.
2010-Aug-04 08:25 UTC
[Xen-users] broken network-support for netBSD-domUs?
Hello. I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which resulted in no network (xennet0 can''t get IPs per dhclient and has no connectivity if set by hand). Tried it with netBSD-5.1-RC3-1 i386 PAE & amd64, netBSD-5.0 and even 4, all with the same result. On a older xen version (3.3.1) networking works fine, so I assume it''s a xen bug, and not a netBSD-kernel one. One server has a pv_ops kernel for Dom0, the other not. A debian test-VM can get a IP just fine per DHCP and connect to the internet. Network-type is briding. not working: host : debnas release : 2.6.32.16-kchris-xen version : #1 SMP Tue Aug 3 08:08:11 CEST 2010 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 1666 hw_caps : bfebfbff:20100800:00000000:00000940:0040e31d:00000000:00000001:00000000 virt_caps : total_memory : 4079 free_memory : 581 node_to_cpu : node0:0-3 node_to_memory : node0:581 node_to_dma32_mem : node0:581 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Mon Aug 02 11:18:41 2010 +0100 21296:e7bd619f8aaa xen_commandline : cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : cc_compile_date : Tue Aug 3 09:11:28 CEST 2010 xend_config_format : 4 working: host : miami release : 2.6.18-92.1.10.el5xen version : #1 SMP Tue Aug 5 08:11:18 EDT 2008 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2000 hw_caps : 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000 virt_caps : hvm total_memory : 16383 free_memory : 1882 node_to_cpu : node0:0-3 node_to_memory : node0:1882 xen_major : 3 xen_minor : 3 xen_extra : .1 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.1.2 20071124 (Red Hat 4.1.2-42) cc_compile_by : root cc_compile_domain : gitco.tld cc_compile_date : Tue Jan 20 23:00:48 CET 2009 xend_config_format : 4 Installing from CD ISO works just fine, the resulting OS still isn''t able to connect to the network with any normal netBSD-provided xen domU kernel. # uname -a NetBSD 5.1_RC3 NetBSD 5.1_RC3 (XEN3PAE_DOMU) #0: Sun Jun 13 03:18:12 UTC 2010 builds@b8.netbsd.org:/home/builds/ab/netbsd-5-1-RC3/i386/201006130031Z-obj/home/builds/ab/netbsd-5-1-RC3/src/sys/arch/i386/compile/XEN3PAE_DOMU i386 # dhclient xennet0 Internet Systems Consortium DHCP Client V3.0.3 Copyright 2004-2005 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/xennet0/00:16:3e:77:91:30 Sending on BPF/xennet0/00:16:3e:77:91:30 Sending on Socket/fallback DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 No DHCPOFFERS received. No working leases in persistent database - sleeping. # # ifconfig xennet0 10.42.42.227 # ifconfig xennet0 10.42.42.227 255.255.255.0 # route add default 10.42.42.1 add net default: gateway 10.42.42.1 # ping 10.42.42.1 PING 10.42.42.1 (10.42.42.1): 56 data bytes ^C ----10.42.42.1 PING Statistics---- 3 packets transmitted, 0 packets received, 100.0% packet loss # ================================================================ debnas:/mnt/data1/build/xen# ping 10.42.42.1 PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=2.28 ms 64 bytes from 10.42.42.1: icmp_seq=2 ttl=64 time=0.819 ms ^C --- 10.42.42.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.819/1.553/2.288/0.735 ms debnas:/mnt/data1/build/xen# ================================================================Debian GNU/Linux 5.0 VM-001 console VM-001 login: root Last login: Fri May 29 00:04:27 UTC 1987 from �анне рэдактарам дазваляе вам наладжваць рэчы, выкарыстоўвая ваш улюбёны тэкставы рэдактар. Неінтэрактыўнае кіраванне ніколі не задае вам on асяроддзі X). Кіра� Linux VM-001 2.6.32.16-kchris-xen #1 SMP Tue Aug 3 08:08:11 CEST 2010 x86_64 VM-001:~# dhclient eth0 Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:16:3e:14:cd:2a Sending on LPF/eth0/00:16:3e:14:cd:2a Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 DHCPOFFER from 10.42.42.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 10.42.42.1 bound to 10.42.42.184 -- renewal in 35198 seconds. VM-001:~# ping 10.42.42.1 PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=1.28 ms ================================================================ (we have a internal network 10.42.42.0/24, 10.42.42.1 is the GW and nameserver) Should I try using a non-pv_op kernel for starters? Does anyone experience the same error with netBSD? -- Mit freundlichen Grüßen, SpiegelEiXXL Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher R. K.
2010-Aug-04 10:29 UTC
[Xen-users] broken network-support for netBSD-domUs?
Hello. I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which resulted in no network (xennet0 can''t get IPs per dhclient and has no connectivity if set by hand). Tried it with netBSD-5.1-RC3-1 i386 PAE & amd64, netBSD-5.0 and even 4, all with the same result. On a older xen version (3.3.1) networking works fine, so I assume it''s a xen bug, and not a netBSD-kernel one. One server has a pv_ops kernel for Dom0, the other not. A debian test-VM can get a IP just fine per DHCP and connect to the internet. Network-type is briding. not working: host : debnas release : 2.6.32.16-kchris-xen version : #1 SMP Tue Aug 3 08:08:11 CEST 2010 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 1666 hw_caps : bfebfbff:20100800:00000000:00000940:0040e31d:00000000:00000001:00000000 virt_caps : total_memory : 4079 free_memory : 581 node_to_cpu : node0:0-3 node_to_memory : node0:581 node_to_dma32_mem : node0:581 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Mon Aug 02 11:18:41 2010 +0100 21296:e7bd619f8aaa xen_commandline : cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : cc_compile_date : Tue Aug 3 09:11:28 CEST 2010 xend_config_format : 4 working: host : miami release : 2.6.18-92.1.10.el5xen version : #1 SMP Tue Aug 5 08:11:18 EDT 2008 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2000 hw_caps : 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000 virt_caps : hvm total_memory : 16383 free_memory : 1882 node_to_cpu : node0:0-3 node_to_memory : node0:1882 xen_major : 3 xen_minor : 3 xen_extra : .1 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.1.2 20071124 (Red Hat 4.1.2-42) cc_compile_by : root cc_compile_domain : gitco.tld cc_compile_date : Tue Jan 20 23:00:48 CET 2009 xend_config_format : 4 Installing from CD ISO works just fine, the resulting OS still isn''t able to connect to the network with any normal netBSD-provided xen domU kernel. # uname -a NetBSD 5.1_RC3 NetBSD 5.1_RC3 (XEN3PAE_DOMU) #0: Sun Jun 13 03:18:12 UTC 2010 builds@b8.netbsd.org:/home/builds/ab/netbsd-5-1-RC3/i386/201006130031Z-obj/home/builds/ab/netbsd-5-1-RC3/src/sys/arch/i386/compile/XEN3PAE_DOMU i386 # dhclient xennet0 Internet Systems Consortium DHCP Client V3.0.3 Copyright 2004-2005 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/xennet0/00:16:3e:77:91:30 Sending on BPF/xennet0/00:16:3e:77:91:30 Sending on Socket/fallback DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 No DHCPOFFERS received. No working leases in persistent database - sleeping. # # ifconfig xennet0 10.42.42.227 # ifconfig xennet0 10.42.42.227 255.255.255.0 # route add default 10.42.42.1 add net default: gateway 10.42.42.1 # ping 10.42.42.1 PING 10.42.42.1 (10.42.42.1): 56 data bytes ^C ----10.42.42.1 PING Statistics---- 3 packets transmitted, 0 packets received, 100.0% packet loss # ================================================================ debnas:/mnt/data1/build/xen# ping 10.42.42.1 PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=2.28 ms 64 bytes from 10.42.42.1: icmp_seq=2 ttl=64 time=0.819 ms ^C --- 10.42.42.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.819/1.553/2.288/0.735 ms debnas:/mnt/data1/build/xen# ================================================================Debian GNU/Linux 5.0 VM-001 console VM-001 login: root Last login: Fri May 29 00:04:27 UTC 1987 from �анне рэдактарам дазваляе вам наладжваць рэчы, выкарыстоўвая ваш улюбёны тэкставы рэдактар. Неінтэрактыўнае кіраванне ніколі не задае вам on асяроддзі X). Кіра� Linux VM-001 2.6.32.16-kchris-xen #1 SMP Tue Aug 3 08:08:11 CEST 2010 x86_64 VM-001:~# dhclient eth0 Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:16:3e:14:cd:2a Sending on LPF/eth0/00:16:3e:14:cd:2a Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 DHCPOFFER from 10.42.42.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 10.42.42.1 bound to 10.42.42.184 -- renewal in 35198 seconds. VM-001:~# ping 10.42.42.1 PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=1.28 ms ================================================================ (we have a internal network 10.42.42.0/24, 10.42.42.1 is the GW and nameserver) Should I try using a non-pv_op kernel for starters? Does anyone experience the same error with netBSD? -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dustin Marquess
2010-Aug-05 14:47 UTC
Re: [Xen-users] broken network-support for netBSD-domUs?
It could be completely unrelated, but it''s known that NetBSD domUs are broken under XenServer. This is due to NetBSD using ''flipping'' mode in its network driver instead of ''copying'' mode: http://mail-index.netbsd.org/port-xen/2010/06/15/msg006105.html -Dustin On Wed, Aug 4, 2010 at 5:29 AM, Christopher R. K. <Feuerball_@gmx.net> wrote:> Hello. > > I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which resulted in no network (xennet0 can''t get IPs per dhclient and has no connectivity if set by hand). > > Tried it with netBSD-5.1-RC3-1 i386 PAE & amd64, netBSD-5.0 and even 4, all with the same result. > > On a older xen version (3.3.1) networking works fine, so I assume it''s a xen bug, and not a netBSD-kernel one. > > One server has a pv_ops kernel for Dom0, the other not. > > A debian test-VM can get a IP just fine per DHCP and connect to the internet. > > Network-type is briding. > > > not working: > host : debnas > release : 2.6.32.16-kchris-xen > version : #1 SMP Tue Aug 3 08:08:11 CEST 2010 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 1666 > hw_caps : bfebfbff:20100800:00000000:00000940:0040e31d:00000000:00000001:00000000 > virt_caps : > total_memory : 4079 > free_memory : 581 > node_to_cpu : node0:0-3 > node_to_memory : node0:581 > node_to_dma32_mem : node0:581 > max_node_id : 0 > xen_major : 4 > xen_minor : 0 > xen_extra : .1-rc5 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : Mon Aug 02 11:18:41 2010 +0100 21296:e7bd619f8aaa > xen_commandline : > cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) > cc_compile_by : root > cc_compile_domain : > cc_compile_date : Tue Aug 3 09:11:28 CEST 2010 > xend_config_format : 4 > > > working: > host : miami > release : 2.6.18-92.1.10.el5xen > version : #1 SMP Tue Aug 5 08:11:18 EDT 2008 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 2000 > hw_caps : 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000 > virt_caps : hvm > total_memory : 16383 > free_memory : 1882 > node_to_cpu : node0:0-3 > node_to_memory : node0:1882 > xen_major : 3 > xen_minor : 3 > xen_extra : .1 > 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.1.2 20071124 (Red Hat 4.1.2-42) > cc_compile_by : root > cc_compile_domain : gitco.tld > cc_compile_date : Tue Jan 20 23:00:48 CET 2009 > xend_config_format : 4 > > Installing from CD ISO works just fine, the resulting OS still isn''t able to connect to the network with any normal netBSD-provided xen domU kernel. > > # uname -a > NetBSD 5.1_RC3 NetBSD 5.1_RC3 (XEN3PAE_DOMU) #0: Sun Jun 13 03:18:12 UTC 2010 builds@b8.netbsd.org:/home/builds/ab/netbsd-5-1-RC3/i386/201006130031Z-obj/home/builds/ab/netbsd-5-1-RC3/src/sys/arch/i386/compile/XEN3PAE_DOMU i386 > # dhclient xennet0 > Internet Systems Consortium DHCP Client V3.0.3 > Copyright 2004-2005 Internet Systems Consortium. > All rights reserved. > For info, please visit http://www.isc.org/products/DHCP > > Listening on BPF/xennet0/00:16:3e:77:91:30 > Sending on BPF/xennet0/00:16:3e:77:91:30 > Sending on Socket/fallback > DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 > DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 11 > DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 14 > DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 10 > DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > # > # ifconfig xennet0 10.42.42.227 > # ifconfig xennet0 10.42.42.227 255.255.255.0 > # route add default 10.42.42.1 > add net default: gateway 10.42.42.1 > # ping 10.42.42.1 > PING 10.42.42.1 (10.42.42.1): 56 data bytes > ^C > ----10.42.42.1 PING Statistics---- > 3 packets transmitted, 0 packets received, 100.0% packet loss > # > > ================================================================> > debnas:/mnt/data1/build/xen# ping 10.42.42.1 > PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. > 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=2.28 ms > 64 bytes from 10.42.42.1: icmp_seq=2 ttl=64 time=0.819 ms > ^C > --- 10.42.42.1 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > rtt min/avg/max/mdev = 0.819/1.553/2.288/0.735 ms > debnas:/mnt/data1/build/xen# > > ================================================================> Debian GNU/Linux 5.0 VM-001 console > > VM-001 login: root > Last login: Fri May 29 00:04:27 UTC 1987 from �анне рэдактарам дазваляе вам наладжваць рэчы, выкарыстоўвая ваш улюбёны тэкставы рэдактар. Неінтэрактыўнае кіраванне ніколі не задае вам on асяроддзі X). Кіра� > Linux VM-001 2.6.32.16-kchris-xen #1 SMP Tue Aug 3 08:08:11 CEST 2010 x86_64 > > VM-001:~# dhclient eth0 > Internet Systems Consortium DHCP Client V3.1.1 > Copyright 2004-2008 Internet Systems Consortium. > All rights reserved. > For info, please visit http://www.isc.org/sw/dhcp/ > > Listening on LPF/eth0/00:16:3e:14:cd:2a > Sending on LPF/eth0/00:16:3e:14:cd:2a > Sending on Socket/fallback > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 > DHCPOFFER from 10.42.42.1 > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > DHCPACK from 10.42.42.1 > bound to 10.42.42.184 -- renewal in 35198 seconds. > > VM-001:~# ping 10.42.42.1 > PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. > 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=1.28 ms > > ================================================================> > (we have a internal network 10.42.42.0/24, 10.42.42.1 is the GW and nameserver) > > > Should I try using a non-pv_op kernel for starters? > Does anyone experience the same error with netBSD? > > -- > GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > 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
Christopher R. K.
2010-Aug-05 15:06 UTC
Re: [Xen-users] broken network-support for netBSD-domUs?
Hrm... thou I''m not using XenServer. The weird thing is, that it is working for a older version of xen. I might should point out, that the 4.0.1-rc3 box is running debian, and the 3.3.1 one is running centOS. Also, I noticed following output in the messages file over night: Aug 4 18:53:54 dhclient: No working leases in persistent database - sleeping. Aug 4 19:00:35 dhclient: send_packet: No buffer space available Aug 4 19:00:45 dhclient: send_packet: No buffer space available Aug 4 19:00:53 dhclient: send_packet: No buffer space available Aug 4 19:01:02 dhclient: send_packet: No buffer space available Aug 4 19:01:15 dhclient: send_packet: No buffer space available May that indeed have something to do with the network drivers included in pv_ops? Are there some greater differences between the ones in pv_op and xen-2.6.18?> It could be completely unrelated, but it''s known that NetBSD domUs are > broken under XenServer. This is due to NetBSD using ''flipping'' mode > in its network driver instead of ''copying'' mode: > > http://mail-index.netbsd.org/port-xen/2010/06/15/msg006105.html > > -Dustin > > On Wed, Aug 4, 2010 at 5:29 AM, Christopher R. K.<Feuerball_@gmx.net> wrote: >> Hello. >> >> I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which resulted in no network (xennet0 can''t get IPs per dhclient and has no connectivity if set by hand). >> >> Tried it with netBSD-5.1-RC3-1 i386 PAE& amd64, netBSD-5.0 and even 4, all with the same result. >> >> On a older xen version (3.3.1) networking works fine, so I assume it''s a xen bug, and not a netBSD-kernel one. >> >> One server has a pv_ops kernel for Dom0, the other not. >> >> A debian test-VM can get a IP just fine per DHCP and connect to the internet. >> >> Network-type is briding. >> >> >> not working: >> host : debnas >> release : 2.6.32.16-kchris-xen >> version : #1 SMP Tue Aug 3 08:08:11 CEST 2010 >> machine : x86_64 >> nr_cpus : 4 >> nr_nodes : 1 >> cores_per_socket : 2 >> threads_per_core : 2 >> cpu_mhz : 1666 >> hw_caps : bfebfbff:20100800:00000000:00000940:0040e31d:00000000:00000001:00000000 >> virt_caps : >> total_memory : 4079 >> free_memory : 581 >> node_to_cpu : node0:0-3 >> node_to_memory : node0:581 >> node_to_dma32_mem : node0:581 >> max_node_id : 0 >> xen_major : 4 >> xen_minor : 0 >> xen_extra : .1-rc5 >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p >> xen_scheduler : credit >> xen_pagesize : 4096 >> platform_params : virt_start=0xffff800000000000 >> xen_changeset : Mon Aug 02 11:18:41 2010 +0100 21296:e7bd619f8aaa >> xen_commandline : >> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >> cc_compile_by : root >> cc_compile_domain : >> cc_compile_date : Tue Aug 3 09:11:28 CEST 2010 >> xend_config_format : 4 >> >> >> working: >> host : miami >> release : 2.6.18-92.1.10.el5xen >> version : #1 SMP Tue Aug 5 08:11:18 EDT 2008 >> machine : x86_64 >> nr_cpus : 4 >> nr_nodes : 1 >> cores_per_socket : 2 >> threads_per_core : 1 >> cpu_mhz : 2000 >> hw_caps : 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000 >> virt_caps : hvm >> total_memory : 16383 >> free_memory : 1882 >> node_to_cpu : node0:0-3 >> node_to_memory : node0:1882 >> xen_major : 3 >> xen_minor : 3 >> xen_extra : .1 >> 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.1.2 20071124 (Red Hat 4.1.2-42) >> cc_compile_by : root >> cc_compile_domain : gitco.tld >> cc_compile_date : Tue Jan 20 23:00:48 CET 2009 >> xend_config_format : 4 >> >> Installing from CD ISO works just fine, the resulting OS still isn''t able to connect to the network with any normal netBSD-provided xen domU kernel. >> >> # uname -a >> NetBSD 5.1_RC3 NetBSD 5.1_RC3 (XEN3PAE_DOMU) #0: Sun Jun 13 03:18:12 UTC 2010 builds@b8.netbsd.org:/home/builds/ab/netbsd-5-1-RC3/i386/201006130031Z-obj/home/builds/ab/netbsd-5-1-RC3/src/sys/arch/i386/compile/XEN3PAE_DOMU i386 >> # dhclient xennet0 >> Internet Systems Consortium DHCP Client V3.0.3 >> Copyright 2004-2005 Internet Systems Consortium. >> All rights reserved. >> For info, please visit http://www.isc.org/products/DHCP >> >> Listening on BPF/xennet0/00:16:3e:77:91:30 >> Sending on BPF/xennet0/00:16:3e:77:91:30 >> Sending on Socket/fallback >> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 >> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 5 >> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 11 >> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 14 >> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 10 >> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 13 >> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 >> No DHCPOFFERS received. >> No working leases in persistent database - sleeping. >> # >> # ifconfig xennet0 10.42.42.227 >> # ifconfig xennet0 10.42.42.227 255.255.255.0 >> # route add default 10.42.42.1 >> add net default: gateway 10.42.42.1 >> # ping 10.42.42.1 >> PING 10.42.42.1 (10.42.42.1): 56 data bytes >> ^C >> ----10.42.42.1 PING Statistics---- >> 3 packets transmitted, 0 packets received, 100.0% packet loss >> # >> >> ================================================================>> >> debnas:/mnt/data1/build/xen# ping 10.42.42.1 >> PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. >> 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=2.28 ms >> 64 bytes from 10.42.42.1: icmp_seq=2 ttl=64 time=0.819 ms >> ^C >> --- 10.42.42.1 ping statistics --- >> 2 packets transmitted, 2 received, 0% packet loss, time 1001ms >> rtt min/avg/max/mdev = 0.819/1.553/2.288/0.735 ms >> debnas:/mnt/data1/build/xen# >> >> ================================================================>> Debian GNU/Linux 5.0 VM-001 console >> >> VM-001 login: root >> Last login: Fri May 29 00:04:27 UTC 1987 from �анне рэдактарам дазваляе вам наладжваць рэчы, выкарыстоўвая ваш улюбёны тэкставы рэдактар. Неінтэрактыўнае кіраванне ніколі не задае вам on асяроддзі X). Кіра� >> Linux VM-001 2.6.32.16-kchris-xen #1 SMP Tue Aug 3 08:08:11 CEST 2010 x86_64 >> >> VM-001:~# dhclient eth0 >> Internet Systems Consortium DHCP Client V3.1.1 >> Copyright 2004-2008 Internet Systems Consortium. >> All rights reserved. >> For info, please visit http://www.isc.org/sw/dhcp/ >> >> Listening on LPF/eth0/00:16:3e:14:cd:2a >> Sending on LPF/eth0/00:16:3e:14:cd:2a >> Sending on Socket/fallback >> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 >> DHCPOFFER from 10.42.42.1 >> DHCPREQUEST on eth0 to 255.255.255.255 port 67 >> DHCPACK from 10.42.42.1 >> bound to 10.42.42.184 -- renewal in 35198 seconds. >> >> VM-001:~# ping 10.42.42.1 >> PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. >> 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=1.28 ms >> >> ================================================================>> >> (we have a internal network 10.42.42.0/24, 10.42.42.1 is the GW and nameserver) >> >> >> Should I try using a non-pv_op kernel for starters? >> Does anyone experience the same error with netBSD? >> >> -- >> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >> >> _______________________________________________ >> 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 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher R. K.
2010-Aug-10 14:37 UTC
Re: [Xen-users] broken network-support for netBSD-domUs?
OK, a little update on this issue: I continue trying installing netBSD (various versions) on a i686 centOS host and tried using non pv_op kernels. My result shows the following: As soon as I update to xen4.0.0, or above (even svn), netBSD network support breaks beyond repairability. This applies to 2.6.18-patched and pv_op kernels alikes. I issues the same steps to configure network on all the different setups, the only setup that started working was the previous one that already worked and the xen3.4.3 i686 build. (for the CentOS Hosts i used the RPMs from gitco.de) Anyone got an idea if there''s gonna be a fix? Or is it possible that the kernels that are out there yet don''t support xen4? Is xen4 already ported to netBSD/openBSD/freeBSD so it would be worth to try if compiling a kernel by hand would solve the issue? Best> Hrm... thou I''m not using XenServer. > The weird thing is, that it is working for a older version of xen. > I might should point out, that the 4.0.1-rc3 box is running debian, > and the 3.3.1 one is running centOS. > Also, I noticed following output in the messages file over night: > > Aug 4 18:53:54 dhclient: No working leases in persistent database - > sleeping. > Aug 4 19:00:35 dhclient: send_packet: No buffer space available > Aug 4 19:00:45 dhclient: send_packet: No buffer space available > Aug 4 19:00:53 dhclient: send_packet: No buffer space available > Aug 4 19:01:02 dhclient: send_packet: No buffer space available > Aug 4 19:01:15 dhclient: send_packet: No buffer space available > > May that indeed have something to do with the network drivers included > in pv_ops? Are there some greater differences between the ones in > pv_op and xen-2.6.18? > >> It could be completely unrelated, but it''s known that NetBSD domUs are >> broken under XenServer. This is due to NetBSD using ''flipping'' mode >> in its network driver instead of ''copying'' mode: >> >> http://mail-index.netbsd.org/port-xen/2010/06/15/msg006105.html >> >> -Dustin >> >> On Wed, Aug 4, 2010 at 5:29 AM, Christopher R. >> K.<Feuerball_@gmx.net> wrote: >>> Hello. >>> >>> I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which >>> resulted in no network (xennet0 can''t get IPs per dhclient and has >>> no connectivity if set by hand). >>> >>> Tried it with netBSD-5.1-RC3-1 i386 PAE& amd64, netBSD-5.0 and even >>> 4, all with the same result. >>> >>> On a older xen version (3.3.1) networking works fine, so I assume >>> it''s a xen bug, and not a netBSD-kernel one. >>> >>> One server has a pv_ops kernel for Dom0, the other not. >>> >>> A debian test-VM can get a IP just fine per DHCP and connect to the >>> internet. >>> >>> Network-type is briding. >>> >>> >>> not working: >>> host : debnas >>> release : 2.6.32.16-kchris-xen >>> version : #1 SMP Tue Aug 3 08:08:11 CEST 2010 >>> machine : x86_64 >>> nr_cpus : 4 >>> nr_nodes : 1 >>> cores_per_socket : 2 >>> threads_per_core : 2 >>> cpu_mhz : 1666 >>> hw_caps : >>> bfebfbff:20100800:00000000:00000940:0040e31d:00000000:00000001:00000000 >>> virt_caps : >>> total_memory : 4079 >>> free_memory : 581 >>> node_to_cpu : node0:0-3 >>> node_to_memory : node0:581 >>> node_to_dma32_mem : node0:581 >>> max_node_id : 0 >>> xen_major : 4 >>> xen_minor : 0 >>> xen_extra : .1-rc5 >>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p >>> xen_scheduler : credit >>> xen_pagesize : 4096 >>> platform_params : virt_start=0xffff800000000000 >>> xen_changeset : Mon Aug 02 11:18:41 2010 +0100 >>> 21296:e7bd619f8aaa >>> xen_commandline : >>> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) >>> cc_compile_by : root >>> cc_compile_domain : >>> cc_compile_date : Tue Aug 3 09:11:28 CEST 2010 >>> xend_config_format : 4 >>> >>> >>> working: >>> host : miami >>> release : 2.6.18-92.1.10.el5xen >>> version : #1 SMP Tue Aug 5 08:11:18 EDT 2008 >>> machine : x86_64 >>> nr_cpus : 4 >>> nr_nodes : 1 >>> cores_per_socket : 2 >>> threads_per_core : 1 >>> cpu_mhz : 2000 >>> hw_caps : >>> 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000 >>> virt_caps : hvm >>> total_memory : 16383 >>> free_memory : 1882 >>> node_to_cpu : node0:0-3 >>> node_to_memory : node0:1882 >>> xen_major : 3 >>> xen_minor : 3 >>> xen_extra : .1 >>> 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.1.2 20071124 (Red Hat 4.1.2-42) >>> cc_compile_by : root >>> cc_compile_domain : gitco.tld >>> cc_compile_date : Tue Jan 20 23:00:48 CET 2009 >>> xend_config_format : 4 >>> >>> Installing from CD ISO works just fine, the resulting OS still isn''t >>> able to connect to the network with any normal netBSD-provided xen >>> domU kernel. >>> >>> # uname -a >>> NetBSD 5.1_RC3 NetBSD 5.1_RC3 (XEN3PAE_DOMU) #0: Sun Jun 13 >>> 03:18:12 UTC 2010 >>> builds@b8.netbsd.org:/home/builds/ab/netbsd-5-1-RC3/i386/201006130031Z-obj/home/builds/ab/netbsd-5-1-RC3/src/sys/arch/i386/compile/XEN3PAE_DOMU >>> i386 >>> # dhclient xennet0 >>> Internet Systems Consortium DHCP Client V3.0.3 >>> Copyright 2004-2005 Internet Systems Consortium. >>> All rights reserved. >>> For info, please visit http://www.isc.org/products/DHCP >>> >>> Listening on BPF/xennet0/00:16:3e:77:91:30 >>> Sending on BPF/xennet0/00:16:3e:77:91:30 >>> Sending on Socket/fallback >>> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 >>> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 5 >>> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 11 >>> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 14 >>> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 10 >>> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 13 >>> DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 >>> No DHCPOFFERS received. >>> No working leases in persistent database - sleeping. >>> # >>> # ifconfig xennet0 10.42.42.227 >>> # ifconfig xennet0 10.42.42.227 255.255.255.0 >>> # route add default 10.42.42.1 >>> add net default: gateway 10.42.42.1 >>> # ping 10.42.42.1 >>> PING 10.42.42.1 (10.42.42.1): 56 data bytes >>> ^C >>> ----10.42.42.1 PING Statistics---- >>> 3 packets transmitted, 0 packets received, 100.0% packet loss >>> # >>> >>> ================================================================>>> >>> debnas:/mnt/data1/build/xen# ping 10.42.42.1 >>> PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. >>> 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=2.28 ms >>> 64 bytes from 10.42.42.1: icmp_seq=2 ttl=64 time=0.819 ms >>> ^C >>> --- 10.42.42.1 ping statistics --- >>> 2 packets transmitted, 2 received, 0% packet loss, time 1001ms >>> rtt min/avg/max/mdev = 0.819/1.553/2.288/0.735 ms >>> debnas:/mnt/data1/build/xen# >>> >>> ================================================================>>> Debian GNU/Linux 5.0 VM-001 console >>> >>> VM-001 login: root >>> Last login: Fri May 29 00:04:27 UTC 1987 from �анне рэдактарам >>> дазваляе вам наладжваць рэчы, выкарыстоўвая ваш улюбёны тэкставы >>> рэдактар. Неінтэрактыўнае кіраванне ніколі не задае вам on >>> асяроддзі X). Кіра� >>> Linux VM-001 2.6.32.16-kchris-xen #1 SMP Tue Aug 3 08:08:11 CEST >>> 2010 x86_64 >>> >>> VM-001:~# dhclient eth0 >>> Internet Systems Consortium DHCP Client V3.1.1 >>> Copyright 2004-2008 Internet Systems Consortium. >>> All rights reserved. >>> For info, please visit http://www.isc.org/sw/dhcp/ >>> >>> Listening on LPF/eth0/00:16:3e:14:cd:2a >>> Sending on LPF/eth0/00:16:3e:14:cd:2a >>> Sending on Socket/fallback >>> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 >>> DHCPOFFER from 10.42.42.1 >>> DHCPREQUEST on eth0 to 255.255.255.255 port 67 >>> DHCPACK from 10.42.42.1 >>> bound to 10.42.42.184 -- renewal in 35198 seconds. >>> >>> VM-001:~# ping 10.42.42.1 >>> PING 10.42.42.1 (10.42.42.1) 56(84) bytes of data. >>> 64 bytes from 10.42.42.1: icmp_seq=1 ttl=64 time=1.28 ms >>> >>> ================================================================>>> >>> (we have a internal network 10.42.42.0/24, 10.42.42.1 is the GW and >>> nameserver) >>> >>> >>> Should I try using a non-pv_op kernel for starters? >>> Does anyone experience the same error with netBSD? >>> >>> -- >>> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! >>> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > 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