[Bug 231274] New: No network within Xen Domain0
https://bugzilla.novell.com/show_bug.cgi?id=231274 Summary: No network within Xen Domain0 Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: Stephan@reLinux.de QAContact: qa@suse.de Hi, I've got a AMD Athlon64X2 4200+ and a MSI K9NU Neo-V motherboard (nVidia M1697) Running the non-xen system everything is O.K., but after booting xen I can't get an network connection from domain 0. I tried: - both 32 and 64 Bit architectures - using a PCI ethernet card instead of onboard controller - DHCP, fixed IP settings and issuing ifconfig manually - disabling bridging within xen - firewall not enabled, ip-forward enabled The only thing that works somehow is a USB-to-ethernet adaptor (pegasus), but that is awfully slow. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231274 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Stephan@reLinux.de ------- Comment #1 from kallan@novell.com 2007-01-02 13:56 MST ------- Please provide the following output from the Xen booted system: 1.cat /proc/interrupts (do the interrupts for the NIC keep incrementing?) 2.ls /sys/class/net 3.ls /etc/sysconfig/network 4.ifconfig 5.ip route Also verify that the network is being controlled by the traditional method with ifup. Xen does not support the NetworkManager method for controlling the network. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231274 Stephan@reLinux.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Stephan@reLinux.de Status|NEEDINFO |NEW Info Provider|Stephan@reLinux.de | ------- Comment #2 from Stephan@reLinux.de 2007-01-03 08:00 MST ------- (In reply to comment #1)
Please provide the following output from the Xen booted system:
1.cat /proc/interrupts (do the interrupts for the NIC keep incrementing?) no, they don't 2.ls /sys/class/net # ls -l /sys/class/net total 0 drwxr-xr-x 3 root root 0 Jan 3 15:44 eth0 drwxr-xr-x 3 root root 0 Jan 3 15:44 lo drwxr-xr-x 4 root root 0 Jan 3 15:44 peth0 drwxr-xr-x 3 root root 0 Jan 3 15:44 sit0 drwxr-xr-x 3 root root 0 Jan 3 15:44 veth1 drwxr-xr-x 3 root root 0 Jan 3 15:44 veth2 drwxr-xr-x 3 root root 0 Jan 3 15:44 veth3 drwxr-xr-x 4 root root 0 Jan 3 15:44 vif0.0 drwxr-xr-x 3 root root 0 Jan 3 15:44 vif0.1 drwxr-xr-x 3 root root 0 Jan 3 15:44 vif0.2 drwxr-xr-x 3 root root 0 Jan 3 15:44 vif0.3 drwxr-xr-x 5 root root 0 Jan 3 15:44 xenbr0
3.ls /etc/sysconfig/network
# ls -l /etc/sysconfig/network/ total 80 -rw-r--r-- 1 root root 9254 Dec 31 14:42 config -rw-r--r-- 1 root root 6988 Dec 31 15:19 dhcp drwxr-xr-x 2 root root 4096 Nov 25 23:26 if-down.d drwxr-xr-x 2 root root 4096 Nov 25 23:26 if-up.d -rw-r--r-- 1 root root 283 Jan 3 15:25 ifcfg-eth-id-00:16:17:90:33:c9 -rw-r--r-- 1 root root 141 Nov 25 13:07 ifcfg-lo -rw-r--r-- 1 root root 27679 Nov 25 13:07 ifcfg.template -rw-r--r-- 1 root root 239 Nov 25 13:07 ifroute-lo drwx------ 2 root root 4096 Nov 25 23:26 providers -rw-r--r-- 1 root root 26 Jan 2 11:05 routes -rw-r--r-- 1 root root 0 Jan 2 11:05 routes.YaST2save drwxr-xr-x 2 root root 4096 Dec 31 14:42 scripts
4.ifconfig
# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:17:90:33:C9 inet addr:192.168.11.10 Bcast:192.168.11.255 Mask:255.255.255.0 inet6 addr: fe80::216:17ff:fe90:33c9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:268 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:11472 (11.2 Kb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:595 errors:0 dropped:0 overruns:0 frame:0 TX packets:595 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:48300 (47.1 Kb) TX bytes:48300 (47.1 Kb) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP MTU:1500 Metric:1 RX packets:1574 errors:0 dropped:0 overruns:0 frame:0 TX packets:1193 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2089546 (1.9 Mb) TX bytes:79971 (78.0 Kb) Interrupt:21 Base address:0xe800 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:268 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11472 (11.2 Kb) TX bytes:0 (0.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:268 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7720 (7.5 Kb) TX bytes:0 (0.0 b)
5.ip route
# ip route 192.168.11.0/24 dev eth0 proto kernel scope link src 192.168.11.10 169.254.0.0/16 dev eth0 scope link 127.0.0.0/8 dev lo scope link default via 192.168.11.6 dev eth0
Also verify that the network is being controlled by the traditional method with ifup. Xen does not support the NetworkManager method for controlling the network.
Yes, that is configured that way.
Maybe also interesting from /var/log/messages: Jan 3 15:44:04 magenta ifup: lo Jan 3 15:44:04 magenta ifup: lo Jan 3 15:44:04 magenta ifup: IP address: 127.0.0.1/8 Jan 3 15:44:04 magenta ifup: Jan 3 15:44:05 magenta ifup: eth0 device: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 60) Jan 3 15:44:05 magenta ifup: eth0 configuration: eth-id-00:16:17:90:33:c9 Jan 3 15:44:05 magenta ifup: eth0 Jan 3 15:44:05 magenta ifup: IP address: 192.168.11.10/24 Jan 3 15:44:05 magenta ifup: Jan 3 15:44:05 magenta ifup: eth1 Jan 3 15:44:05 magenta syslog-ng[2315]: Changing permissions on special file /dev/xconsole Jan 3 15:44:05 magenta syslog-ng[2315]: Changing permissions on special file /dev/tty10 Jan 3 15:44:05 magenta ifup: No configuration found for eth1 Jan 3 15:44:05 magenta auditd: Config file /etc/audit/auditd.conf doesn't exist, skipping Jan 3 15:44:06 magenta auditd[3013]: Init complete, auditd 1.2.6 listening for events Jan 3 15:44:08 magenta rcpowersaved: s2ram does not know your machine. See 's2ram -i' for details. (127) Jan 3 15:44:08 magenta rcpowersaved: Use SUSPEND2RAM_FORCE=yes to override this detection. Jan 3 15:44:08 magenta kernel: klogd 1.4.1, log source = /proc/kmsg started. Jan 3 15:44:08 magenta kernel: ACPI: Power Button (FF) [PWRF] Jan 3 15:44:08 magenta kernel: ACPI: Power Button (CM) [PWRB] Jan 3 15:44:08 magenta kernel: audit(1167835445.993:3): audit_pid=3013 old=0 by auid=4294967295 Jan 3 15:44:08 magenta kernel: uli526x: eth0 NIC Link is Up 100 Mbps Full duplex Jan 3 15:44:08 magenta ifup: vif0.3 Jan 3 15:44:08 magenta ifup: No configuration found for vif0.3 Jan 3 15:44:08 magenta ifup: veth1 Jan 3 15:44:08 magenta ifup: No configuration found for veth1 Jan 3 15:44:08 magenta kernel: NET: Registered protocol family 10 Jan 3 15:44:08 magenta kernel: lo: Disabled Privacy Extensions Jan 3 15:44:08 magenta kernel: IPv6 over IPv4 tunneling driver Jan 3 15:44:08 magenta ifup: veth2 Jan 3 15:44:08 magenta ifup: veth0 Jan 3 15:44:08 magenta ifup: No configuration found for veth2 Jan 3 15:44:08 magenta ifup: No configuration found for veth0 Jan 3 15:44:08 magenta sshd[3449]: Server listening on :: port 22. Jan 3 15:44:08 magenta ifup: vif0.0 Jan 3 15:44:08 magenta ifup: vif0.1 Jan 3 15:44:08 magenta ifup: No configuration found for vif0.0 Jan 3 15:44:08 magenta ifup: No configuration found for vif0.1 Jan 3 15:44:08 magenta ifup: vif0.2 Jan 3 15:44:08 magenta ifup: No configuration found for vif0.2 Jan 3 15:44:09 magenta ifup: veth3 Jan 3 15:44:09 magenta ifup: No configuration found for veth3 Jan 3 15:44:09 magenta ifup: sit0 Jan 3 15:44:09 magenta ifup: No configuration found for sit0 kind regards Stephan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231274 ------- Comment #3 from Stephan@reLinux.de 2007-01-04 08:15 MST ------- (In reply to comment #1)
Please provide the following output from the Xen booted system: Hello, Kirk,
I've got some additional information. Every time I start or stop bridging the ethernet port gets broken. I can reactivate it by issuing ifconfig down and up commands as shown below. Kind regards Stephan magenta:~ # /etc/xen/scripts/network-bridge start eth0 device: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 60) eth0 configuration: eth-id-00:16:17:90:33:c9 eth0 IP address: 192.168.11.10/24 eth0 device: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 60) eth0 configuration: eth-id-00:16:17:90:33:c9 Nothing to flush. Nothing to flush. Waiting for peth0 to negotiate link...........(link isnt in running state) eth0 eth0 configuration: eth-id-00:16:17:90:33:c9 eth0 IP address: 192.168.11.10/24 magenta:~ # ping 192.168.11.8 PING 192.168.11.8 (192.168.11.8) 56(84) bytes of data. --- 192.168.11.8 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms /var/log/messages: Jan 4 14:57:03 magenta ifup: xenbr0 Jan 4 14:57:03 magenta ifup: No configuration found for xenbr0 Jan 4 14:57:03 magenta ifup: eth0 device: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 60) Jan 4 14:57:03 magenta ifup: eth0 configuration: eth-id-00:16:17:90:33:c9 Jan 4 14:57:03 magenta ifup: eth0 Jan 4 14:57:03 magenta ifup: IP address: 192.168.11.10/24 Jan 4 14:57:03 magenta ifup: Jan 4 14:57:03 magenta ifdown: eth0 device: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 60) Jan 4 14:57:03 magenta ifdown: eth0 configuration: eth-id-00:16:17:90:33:c9 Jan 4 14:57:03 magenta kernel: eth0 renamed to peth0 Jan 4 14:57:03 magenta kernel: veth0 renamed to eth0 Jan 4 14:57:04 magenta kernel: device vif0.0 entered promiscuous mode Jan 4 14:57:04 magenta kernel: xenbr0: port 1(vif0.0) entering learning state Jan 4 14:57:04 magenta kernel: xenbr0: topology change detected, propagating Jan 4 14:57:04 magenta kernel: xenbr0: port 1(vif0.0) entering forwarding state Jan 4 14:57:04 magenta kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready magenta:~ # ifconfig peth0 down magenta:~ # ifconfig peth0 up magenta:~ # ping 192.168.11.8 PING 192.168.11.8 (192.168.11.8) 56(84) bytes of data. 64 bytes from 192.168.11.8: icmp_seq=1 ttl=64 time=0.881 ms 64 bytes from 192.168.11.8: icmp_seq=2 ttl=64 time=0.140 ms /var/log/messages: Jan 4 14:57:14 magenta kernel: device peth0 entered promiscuous mode Jan 4 14:57:14 magenta ifup: eth0 Jan 4 14:57:14 magenta ifup: eth0 configuration: eth-id-00:16:17:90:33:c9 Jan 4 14:57:14 magenta ifup: eth0 Jan 4 14:57:14 magenta ifup: IP address: 192.168.11.10/24 Jan 4 14:57:14 magenta ifup: Jan 4 14:57:24 magenta kernel: eth0: no IPv6 routers present magenta:~ # /etc/xen/scripts/network-bridge stop eth0 eth0 configuration: eth-id-00:16:17:90:33:c9 Nothing to flush. eth0 device: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 60) eth0 configuration: eth-id-00:16:17:90:33:c9 eth0 IP address: 192.168.11.10/24 magenta:~ # ping 192.168.11.8 PING 192.168.11.8 (192.168.11.8) 56(84) bytes of data.
From 192.168.11.10 icmp_seq=1 Destination Host Unreachable
/var/log/messages: Jan 4 15:45:01 magenta su: (to beagleindex) root on none Jan 4 15:45:20 magenta su: (to beagleindex) root on none Jan 4 15:49:00 magenta syslog-ng[2326]: STATS: dropped 0 Jan 4 15:49:10 magenta zmd: ShutdownManager (WARN): Preparing to sleep... Jan 4 15:49:10 magenta zmd: ShutdownManager (WARN): Going to sleep, waking up at 01/05/2007 14:39:10 Jan 4 16:00:20 magenta kernel: xenbr0: port 2(peth0) entering disabled state Jan 4 16:00:26 magenta kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready Jan 4 16:00:29 magenta kernel: uli526x: peth0 NIC Link is Up 100 Mbps Full duplex Jan 4 16:00:29 magenta kernel: ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready Jan 4 16:00:29 magenta kernel: xenbr0: port 2(peth0) entering learning state Jan 4 16:00:29 magenta kernel: xenbr0: topology change detected, propagating Jan 4 16:00:29 magenta kernel: xenbr0: port 2(peth0) entering forwarding state Jan 4 16:01:53 magenta kernel: xenbr0: port 2(peth0) entering disabled state Jan 4 16:02:00 magenta kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready Jan 4 16:02:03 magenta kernel: uli526x: peth0 NIC Link is Up 100 Mbps Full duplex Jan 4 16:02:03 magenta kernel: ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready Jan 4 16:02:03 magenta kernel: xenbr0: port 2(peth0) entering learning state Jan 4 16:02:03 magenta kernel: xenbr0: topology change detected, propagating Jan 4 16:02:03 magenta kernel: xenbr0: port 2(peth0) entering forwarding state Jan 4 16:02:16 magenta kernel: xenbr0: port 1(vif0.0) entering disabled state Jan 4 16:02:16 magenta ifdown: eth0 Jan 4 16:02:16 magenta ifdown: eth0 configuration: eth-id-00:16:17:90:33:c9 Jan 4 16:02:17 magenta kernel: xenbr0: port 2(peth0) entering disabled state Jan 4 16:02:17 magenta kernel: device peth0 left promiscuous mode Jan 4 16:02:17 magenta kernel: xenbr0: port 2(peth0) entering disabled state Jan 4 16:02:17 magenta kernel: device vif0.0 left promiscuous mode Jan 4 16:02:17 magenta kernel: xenbr0: port 1(vif0.0) entering disabled state Jan 4 16:02:17 magenta kernel: eth0 renamed to veth0 Jan 4 16:02:17 magenta kernel: peth0 renamed to eth0 Jan 4 16:02:17 magenta ifup: eth0 device: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 60) Jan 4 16:02:17 magenta ifup: eth0 configuration: eth-id-00:16:17:90:33:c9 Jan 4 16:02:17 magenta kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 4 16:02:17 magenta ifup: eth0 Jan 4 16:02:17 magenta ifup: IP address: 192.168.11.10/24 Jan 4 16:02:17 magenta ifup: Jan 4 16:02:17 magenta ifdown: xenbr0 Jan 4 16:02:17 magenta ifdown: Interface not available and no configuration found. magenta:~ # ifconfig eth0 down magenta:~ # ifconfig eth0 up /var/log/messages: Jan 4 16:03:11 magenta kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 4 16:03:14 magenta kernel: uli526x: eth0 NIC Link is Up 100 Mbps Full duplex Jan 4 16:03:14 magenta kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231274 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Stephan@reLinux.de ------- Comment #4 from kallan@novell.com 2007-01-04 08:28 MST ------- The key here is that when you cat /proc/interrupts you see that interrupts have stopped incrementing on the Etherenet interface. In the past, when this has happened it was due to IRQ routing problems with the BIOS. Normal linux would work since interrupt assignments are different between normal and Xen. If you unload and reload the LAN driver and interrupts start again then it is something other than IRQ routing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231274 Stephan@reLinux.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|Stephan@reLinux.de | ------- Comment #5 from Stephan@reLinux.de 2007-01-04 10:33 MST ------- (In reply to comment #4)
The key here is that when you cat /proc/interrupts you see that interrupts have stopped incrementing on the Etherenet interface. In the past, when this has happened it was due to IRQ routing problems with the BIOS. Normal linux would work since interrupt assignments are different between normal and Xen.
If you unload and reload the LAN driver and interrupts start again then it is something other than IRQ routing.
I verified it once again. When the interface does not work no interrupts are counted. There are broadcats in my network and I tried to ping from the outside and even then no interrupts occur. Anything else to analyze? magenta:~ # cat /proc/interrupts | grep eth0 22: 2401679 0 Phys-irq eth0 magenta:~ # cat /proc/interrupts | grep eth0 22: 2401679 0 Phys-irq eth0 magenta:~ # cat /proc/interrupts | grep eth0 22: 2401679 0 Phys-irq eth0 magenta:~ # ping 192.168.11.6 PING 192.168.11.6 (192.168.11.6) 56(84) bytes of data. --- 192.168.11.6 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms magenta:~ # cat /proc/interrupts | grep eth0 22: 2401679 0 Phys-irq eth0 magenta:~ # cat /proc/interrupts | grep eth0 22: 2401679 0 Phys-irq eth0 magenta:~ # ifconfig eth0 down magenta:~ # cat /proc/interrupts | grep eth0 magenta:~ # ifconfig eth0 up magenta:~ # cat /proc/interrupts | grep eth0 22: 2401684 0 Phys-irq eth0 magenta:~ # cat /proc/interrupts | grep eth0 22: 2401687 0 Phys-irq eth0 magenta:~ # ping 192.168.11.6 PING 192.168.11.6 (192.168.11.6) 56(84) bytes of data. 64 bytes from 192.168.11.6: icmp_seq=1 ttl=64 time=0.396 ms 64 bytes from 192.168.11.6: icmp_seq=2 ttl=64 time=0.240 ms --- 192.168.11.6 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.240/0.318/0.396/0.078 ms magenta:~ # route add default gw 192.168.11.6 magenta:~ # cat /proc/interrupts | grep eth0 22: 2401948 0 Phys-irq eth0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231274 fkohler@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkohler@novell.com ------- Comment #6 from fkohler@novell.com 2007-03-01 12:19 MST ------- resolved in b5 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com