[Bug 205092] New: tg3 NetXtreme BCM5752 Gigabit Ethernet driver does not work with XEN guest.
https://bugzilla.novell.com/show_bug.cgi?id=205092 Summary: tg3 NetXtreme BCM5752 Gigabit Ethernet driver does not work with XEN guest. Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: Wojciech.Szenajch@bull.com.pl QAContact: qa@suse.de tg3 driver works correctly with normal smp kernel and Xen kernel for domain 0. It does not work for Xen guest paravirtual with OpenSuSE 10.1 installed (from DVD image) and also does not work for virutal Windows XP SP2 experimental installation (XP boots successfuly). Domain 0 kernel: 2.6.16.21-0.13-xen. Guest installation made for 2.6.16.21-0.13-xen. System boots but DHCP fails. Also setting static IP address does not help. I also created working guest on another PC: SuSE 10.1 with different ethernet card and upgraded system applying all relevant patches for the day 8.11.2006 to guest system. Next I moved this quest to machine with tg3 driver used. Xen guest successfully booted but ethernet did not work also for 2.6.16.21-0.13-xen kernel on Xen guest system. Ethernet driver details: 42: udi = '/org/freedesktop/Hal/devices/net_00_15_c5_1d_ca_1e' info.capabilities = { 'net', 'net.80203' } info.category = 'net.80203' info.parent = '/org/freedesktop/Hal/devices/pci_14e4_1600' info.product = 'Networking Interface' info.udi = '/org/freedesktop/Hal/devices/net_00_15_c5_1d_ca_1e' linux.hotplug_type = 2 (0x2) linux.subsystem = 'net' linux.sysfs_path = '/sys/class/net/eth0' net.80203.mac_address = 93501377054ull (0x15c51dca1eull) net.address = '00:15:c5:1d:ca:1e' net.arp_proto_hw_id = 1 (0x1) net.interface = 'eth0' net.interface_up = false net.linux.ifindex = 2 (0x2) net.physical_device = '/org/freedesktop/Hal/devices/pci_14e4_1600' 43: udi = '/org/freedesktop/Hal/devices/pci_14e4_1600' info.bus = 'pci' info.linux.driver = 'tg3' info.parent = '/org/freedesktop/Hal/devices/pci_8086_27d4' info.product = 'NetXtreme BCM5752 Gigabit Ethernet PCI Express' info.udi = '/org/freedesktop/Hal/devices/pci_14e4_1600' info.vendor = 'Broadcom Corporation' linux.hotplug_type = 1 (0x1) linux.subsystem = 'pci' linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0' linux.sysfs_path_device = '/sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0' pci.device_class = 2 (0x2) pci.device_protocol = 0 (0x0) pci.device_subclass = 0 (0x0) pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0' pci.product = 'NetXtreme BCM5752 Gigabit Ethernet PCI Express' pci.product_id = 5632 (0x1600) pci.subsys_product = 'Unknown (0x01cc)' pci.subsys_product_id = 460 (0x1cc) pci.subsys_vendor = 'Dell' pci.subsys_vendor_id = 4136 (0x1028) pci.vendor = 'Broadcom Corporation' pci.vendor_id = 5348 (0x14e4) -- 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=205092 Wojciech.Szenajch@bull.com.pl changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Wojciech.Szenajch@bull.com.pl ------- Comment #1 from Wojciech.Szenajch@bull.com.pl 2006-09-12 06:40 MST ------- For installation from DVD image oryginal kernel version was 2.6.16.13-4-xen. Newer version 2.6.16.21-0.13-xen reported before patching is a mistake. After patching this new kernel was installed on Xen quest also. -- 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=205092 cgriffin@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cgriffin@novell.com |kallan@novell.com -- 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=205092 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Wojciech.Szenajch@bull.com.pl ------- Comment #2 from kallan@novell.com 2006-09-26 15:07 MST -------
From domain 0, please provide the output from 'ifconfig' and 'ip route'. Also attach the config file used to start the paravirtualized guest. This file is usually in the /etc/xen/vm directory.
From the running paravirtualized guest, please provide the output from 'ls /sys/class/net'. For each Ethernet interface listed, cat the 'address' file, e.g. 'cat /sys/class/net/eth2/address'. Also provide the output from, 'ls /etc/sysconfig/network'. If domain 0 is not configured right, some or all of this information may not exist.
Thanks for providing all this information. -- 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=205092 ------- Comment #3 from Wojciech.Szenajch@bull.com.pl 2006-09-27 04:24 MST ------- Here is the requested information: ifconfig from domain 0: eth0 Link encap:Ethernet HWaddr 00:15:C5:1D:CA:1E inet addr:130.22.115.101 Bcast:130.22.115.255 Mask:255.255.255.0 inet6 addr: fe80::215:c5ff:fe1d:ca1e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4096 errors:0 dropped:0 overruns:0 frame:0 TX packets:1415 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:876168 (855.6 Kb) TX bytes:255302 (249.3 Kb) Interrupt:18 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:237 errors:0 dropped:0 overruns:0 frame:0 TX packets:237 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:19328 (18.8 Kb) TX bytes:19328 (18.8 Kb) vif1.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:40 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:20528 (20.0 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:40 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:19968 (19.5 Kb) TX bytes:0 (0.0 b) ip route from domain 0: 130.22.115.0/24 dev eth0 proto kernel scope link src 130.22.115.101 127.0.0.0/8 dev lo scope link default via 130.22.115.5 dev eth0 Xen paravirutalized guest config file: disk = [ 'file:/var/lib/xen/images/suse10_1vm1/hda,hda,w', 'file:/var/lib/xen/images/suse10_1vm1/hdb,hdb,w', 'file:/root/SUSE-Linux-10.1-GM-DVD-i386.iso,hdc,r' ] memory = 256 vcpus = 2 builder = 'linux' name = 'suse10_1vm1' vif = [ 'mac=00:16:3e:f0:26:e0' ] localtime = 1 on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' extra = ' TERM=xterm' bootloader = '/usr/lib/xen/boot/domUloader.py' bootentry = 'hda1:/boot/vmlinuz-xen,/boot/initrd-xen'
From the running paravirtualized guest: ls /sys/class/net: eth0 lo sit0
cat /sys/class/net/eth0/address 00:16:3e:f0:26:e0 cat /sys/class/net/lo/address 00:00:00:00:00:00 cat /sys/class/net/sit0/address 00:00:00:00 ls /etc/sysconfig/network config if-up.d ifcfg.template providers dhcp ifcfg-eth-id-00:16:3e:f0:26:e0 ifroute-lo routes if-down.d ifcfg-lo Additionally ifconfig shows no IP address: ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3E:F0:26:E0 inet6 addr: fe80::216:3eff:fef0:26e0/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:53 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:28198 (27.5 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:26 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2084 (2.0 Kb) TX bytes:2084 (2.0 Kb) End of paravirtual guest information. Notes: 1. Real value of IP class was changed in this report because of security reasons. 2. This report was entered from domain 0 as a proof that tg3 in domain 0 works correctly and fails on guest system only. -- 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=205092 Wojciech.Szenajch@bull.com.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Wojciech.Szenajch@bull.com.p| |l | ------- Comment #4 from Wojciech.Szenajch@bull.com.pl 2006-09-27 04:29 MST ------- Changing status back to Assigned. -- 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=205092 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |Wojciech.Szenajch@bull.com.pl ------- Comment #5 from kallan@novell.com 2006-09-27 09:25 MST ------- All the configuration looks good except for the ifconfig from domain 0. From domain 0's ifconfig, vif0.0 and peth0 are missing. Without vif0.0 and peth0, the guest's networking wont work. We now need to find out why they are missing. Edit the '/etc/xen/scripts/network-bridge' file and add the line, 'set -x' just after the initial block of comments. With domain 0 running without any guest running, try the following: /etc/xen/scripts/network-bridge stop /etc/xen/scripts/network-bridge start Capture and attach the output from the '/etc/xen/scripts/network-bridge start'. This should tell us why the vif0.0 and the peth0 fail to get created. -- 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=205092 Wojciech.Szenajch@bull.com.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Wojciech.Szenajch@bull.com.p| |l | ------- Comment #6 from Wojciech.Szenajch@bull.com.pl 2006-09-28 05:38 MST ------- I installed latest kernel patch upgrading to 2.6.16.21-0.25-xen. It is possible that this changed situation that tg3 problem was moved to another place. I reproduced problem on another machine with NEC 82540EM Ethernet. With this card XEN guest network does not work if NetworkManager is used in domain 0. This was the case of my laptop with tg3 driver. It seems that hotplug option is not acceptable for XEN also (I have no time to repeat this test on another machine). So, I set configurations for using ifup methods and auto mode. this made XEN guest network working once again with NEC Ethernet and made missing vif0.0 and peth0 to appear on machine with tg3 driver. But domain 0 network stopped working with XEN started with tg3 driver! Next, in /etc/rc.d/rc5.d I renamed links to ../xend and ../xendomains and rebooted machine back to XEN kernel but without xend started. ifconfig reported: eth0 Link encap:Ethernet HWaddr 00:15:C5:1D:CA:1E inet addr:130.22.115.101 Bcast:130.22.115.255 Mask:255.255.255.0 inet6 addr: fe80::215:c5ff:fe1d:ca1e/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:493 errors:0 dropped:0 overruns:0 frame:0 TX packets:233 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:52715 (51.4 Kb) TX bytes:20413 (19.9 Kb) Interrupt:18 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:76 errors:0 dropped:0 overruns:0 frame:0 TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6224 (6.0 Kb) TX bytes:6224 (6.0 Kb) Network worked correctly in domain 0. Next I manually started: /etc/rc.d/xend start: Starting xend done ifconfig reported: eth0 Link encap:Ethernet HWaddr 00:15:C5:1D:CA:1E inet addr:130.22.115.101 Bcast:130.22.115.255 Mask:255.255.255.0 inet6 addr: fe80::215:c5ff:fe1d:ca1e/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1210 (1.1 Kb) TX bytes:3180 (3.1 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:95 errors:0 dropped:0 overruns:0 frame:0 TX packets:95 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7310 (7.1 Kb) TX bytes:7310 (7.1 Kb) peth0 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:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1265 (1.2 Kb) TX bytes:0 (0.0 b) Interrupt:18 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:19 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3180 (3.1 Kb) TX bytes:1210 (1.1 Kb) 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:36 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:4129 (4.0 Kb) TX bytes:0 (0.0 b) IP address for eth0 is reported but network did not work. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 130.22.115.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo Missing deafault route. Manual adding it did not help. Ping to internal address worked: # ping 130.22.115.101 PING 130.22.115.101 (130.22.115.101) 56(84) bytes of data. 64 bytes from 130.22.115.101: icmp_seq=1 ttl=64 time=0.048 ms 64 bytes from 130.22.115.101: icmp_seq=2 ttl=64 time=0.048 ms --- 130.22.115.101 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.048/0.048/0.048/0.000 ms Ping to other machine in the same network failed: # ping 130.22.115.7 PING 130.22.115.7 (130.22.115.7) 56(84) bytes of data. --- 130.22.115.7 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms During xend start the following mesages apperared in /var/log/messages: Sep 28 12:04:11 d820wszena syslog-ng[2606]: Changing permissions on special file /dev/xconsole Sep 28 12:04:11 d820wszena syslog-ng[2606]: Changing permissions on special file /dev/tty10 Sep 28 12:04:11 d820wszena kernel: blkif_init: reqs=64, pages=704, mmap_vstart=0xf1800000 Sep 28 12:04:11 d820wszena ifup: veth1 Sep 28 12:04:11 d820wszena ifup: No configuration found for veth1 Sep 28 12:04:11 d820wszena ifup: veth5 Sep 28 12:04:11 d820wszena ifup: No configuration found for veth5 Sep 28 12:04:11 d820wszena ifup: veth0 Sep 28 12:04:11 d820wszena ifup: No configuration found for veth0 Sep 28 12:04:11 d820wszena ifup: vif0.0 Sep 28 12:04:11 d820wszena ifup: vif0.1 Sep 28 12:04:11 d820wszena ifup: No configuration found for vif0.0 Sep 28 12:04:11 d820wszena ifup: No configuration found for vif0.1 Sep 28 12:04:11 d820wszena ifup: veth2 Sep 28 12:04:11 d820wszena ifup: No configuration found for veth2 Sep 28 12:04:11 d820wszena ifup: vif0.5 Sep 28 12:04:11 d820wszena ifup: No configuration found for vif0.5 Sep 28 12:04:11 d820wszena ifup: vif0.3 Sep 28 12:04:11 d820wszena ifup: vif0.4 Sep 28 12:04:11 d820wszena ifup: No configuration found for vif0.3 Sep 28 12:04:11 d820wszena ifup: No configuration found for vif0.4 Sep 28 12:04:11 d820wszena ifup: vif0.2 Sep 28 12:04:11 d820wszena ifup: veth3 Sep 28 12:04:12 d820wszena ifup: No configuration found for vif0.2 Sep 28 12:04:11 d820wszena ifup: veth7 Sep 28 12:04:12 d820wszena ifup: veth6 Sep 28 12:04:12 d820wszena ifup: vif0.7 Sep 28 12:04:12 d820wszena ifup: vif0.6 Sep 28 12:04:12 d820wszena ifup: veth4 Sep 28 12:04:12 d820wszena ifup: No configuration found for veth3 Sep 28 12:04:12 d820wszena ifup: No configuration found for veth7 Sep 28 12:04:12 d820wszena ifup: No configuration found for veth6 Sep 28 12:04:12 d820wszena ifup: No configuration found for vif0.7 Sep 28 12:04:12 d820wszena ifup: No configuration found for vif0.6 Sep 28 12:04:12 d820wszena ifup: No configuration found for veth4 Sep 28 12:04:14 d820wszena xenstored: Checking store ... Sep 28 12:04:14 d820wszena xenstored: Checking store complete. Sep 28 12:04:14 d820wszena xenstored: Checking store ... Sep 28 12:04:14 d820wszena xenstored: Checking store complete. Sep 28 12:04:14 d820wszena kernel: Setting mem allocation to 1938432 kiB Sep 28 12:04:14 d820wszena kernel: Bridge firewalling registered Sep 28 12:04:15 d820wszena ifup: xenbr0 Sep 28 12:04:15 d820wszena ifup: No configuration found for xenbr0 Sep 28 12:04:15 d820wszena ifup: eth0 device: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02) Sep 28 12:04:15 d820wszena ifup: eth0 configuration: eth-id-00:15:c5:1d:ca:1e Sep 28 12:04:15 d820wszena ifup-dhcp: eth0 IP address: 130.22.115.101/24 (DHCP was already running) Sep 28 12:04:15 d820wszena ifdown: eth0 device: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02) Sep 28 12:04:15 d820wszena ifdown: eth0 configuration: eth-id-00:15:c5:1d:ca:1e Sep 28 12:04:15 d820wszena dhcpcd[3278]: terminating on signal 15 Sep 28 12:04:15 d820wszena modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf Sep 28 12:04:16 d820wszena kernel: eth0 renamed to peth0 Sep 28 12:04:16 d820wszena kernel: veth0 renamed to eth0 Sep 28 12:04:16 d820wszena kernel: device vif0.0 entered promiscuous mode Sep 28 12:04:16 d820wszena kernel: xenbr0: port 1(vif0.0) entering learning state Sep 28 12:04:16 d820wszena kernel: xenbr0: topology change detected, propagating Sep 28 12:04:16 d820wszena kernel: xenbr0: port 1(vif0.0) entering forwarding state Sep 28 12:04:16 d820wszena kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready Sep 28 12:04:18 d820wszena kernel: tg3: peth0: Link is up at 100 Mbps, full duplex. Sep 28 12:04:18 d820wszena kernel: tg3: peth0: Flow control is on for TX and on for RX. Sep 28 12:04:18 d820wszena kernel: ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready Sep 28 12:04:18 d820wszena kernel: device peth0 entered promiscuous mode Sep 28 12:04:18 d820wszena ifup: eth0 Sep 28 12:04:18 d820wszena ifup: eth0 configuration: eth-id-00:15:c5:1d:ca:1e Sep 28 12:04:18 d820wszena kernel: xenbr0: port 2(peth0) entering learning state Sep 28 12:04:18 d820wszena kernel: xenbr0: topology change detected, propagating Sep 28 12:04:18 d820wszena kernel: xenbr0: port 2(peth0) entering forwarding state Sep 28 12:04:18 d820wszena ifup-dhcp: eth0 (DHCP) Sep 28 12:04:18 d820wszena ifup-dhcp: . Sep 28 12:04:19 d820wszena ifup-dhcp: . Sep 28 12:04:20 d820wszena ifup-dhcp: . Sep 28 12:04:21 d820wszena ifup-dhcp: . Sep 28 12:04:22 d820wszena ifup-dhcp: . Sep 28 12:04:23 d820wszena ifup-dhcp: no IP address yet... backgrounding. Sep 28 12:04:28 d820wszena kernel: eth0: no IPv6 routers present Sep 28 12:08:53 d820wszena ifstatus: eth0 Sep 28 12:08:53 d820wszena ifstatus: eth0 configuration: eth-id-00:15:c5:1d:ca:1e Sep 28 12:08:53 d820wszena ifstatus-dhcp: eth0 DHCP client (dhcpcd) is running Sep 28 12:08:53 d820wszena ifstatus: eth0 IP address: 130.22.115.101/24 Sep 28 12:08:53 d820wszena ifstatus: peth0 device: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02) Sep 28 12:08:53 d820wszena ifstatus: No configuration found for peth0 Sep 28 12:08:54 d820wszena ifstatus: veth1 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for veth1 Sep 28 12:08:54 d820wszena ifstatus: veth2 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for veth2 Sep 28 12:08:54 d820wszena ifstatus: veth3 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for veth3 Sep 28 12:08:54 d820wszena ifstatus: veth4 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for veth4 Sep 28 12:08:54 d820wszena ifstatus: veth5 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for veth5 Sep 28 12:08:54 d820wszena ifstatus: veth6 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for veth6 Sep 28 12:08:54 d820wszena ifstatus: veth7 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for veth7 Sep 28 12:08:54 d820wszena ifstatus: vif0.0 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.0 Sep 28 12:08:54 d820wszena ifstatus: vif0.1 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.1 Sep 28 12:08:54 d820wszena ifstatus: vif0.2 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.2 Sep 28 12:08:54 d820wszena ifstatus: vif0.3 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.3 Sep 28 12:08:54 d820wszena ifstatus: vif0.4 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.4 Sep 28 12:08:54 d820wszena ifstatus: vif0.5 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.5 Sep 28 12:08:54 d820wszena ifstatus: vif0.6 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.6 Sep 28 12:08:54 d820wszena ifstatus: vif0.7 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for vif0.7 Sep 28 12:08:54 d820wszena ifstatus: xenbr0 Sep 28 12:08:54 d820wszena ifstatus: No configuration found for xenbr0 Sep 28 12:08:54 d820wszena ifstatus: lo Sep 28 12:08:54 d820wszena ifstatus: IP address: 127.0.0.1/8 Please notice DHCP problem (backgrounding). Manual execution of xend stop; network stop; network start did not clean situation with XEN kernel. It also caused NEC Ethernet card to stop working! Command: network restart correctly stopped and restablished network configuration if xend start was not executed after reboot. Any suggestions? Note: additionally to deactivating NetworkManager I unconfigured my Intel/PRO wireless card to have only NetExtreme BCM5752 present in configuration. -- 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=205092 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |Wojciech.Szenajch@bull.compl ------- Comment #7 from kallan@novell.com 2006-09-28 11:45 MST ------- The README.SuSE for Xen indicates that Xen bridging currently does not work with the NetworkManager. If I understand correctly, once ifup method was used, the box with the NEC NIC work OK with Xen, but the box with the BCM5752 still does not work with Xen Does this also mean that if you do '/etc/xen/scripts/network-bridge stop' that ping starts working on domain0 and doing '/etc/xen/scripts/network-bridge start' that ping stops on the box with the tg3? It would still be interesting to see the output from '/etc/xen/scripts/network-bridge start' with the 'set -x' in network-bridge. Another thing to check is if SuSEfirewall2 is running. If it is, check that there is FW_FORWARD_ALWAYS_INOUT_DEV=”xenbr0” in /etc/syscofnig/SuSEfirewall2. Unfortunately, we do not have a BCM5752 here to test with. We successfully test on the BCM5704 and the BCM5751 using tg3 all the time. -- 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=205092 Wojciech.Szenajch@bull.com.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Wojciech.Szenajch@bull.com.p| |l | ------- Comment #8 from Wojciech.Szenajch@bull.com.pl 2006-10-02 07:38 MST ------- The problem was with firewall. Setting FW_FORWARD_ALWAYS_INOUT_DEV="xenbr0" was the issue. Now it works. the problem is that README.SuSE file is outdated and this setting is not documented there. There is also nothing about it in XEN chapter of SuSE help. I wrongly assumed that studying files from /etc/sysconfig is not required if you have Yast tool. It was true for most services I used. In README.SuSE is written: 'You also need to enable forwarding (FW_FORWARD="yes" )'. It was not required on my system. Please update SuSE XEN documentation. Please close this bug if if you decide to open another one cocncerning SuSE XEN documentation or just correct it as a part of this bug. Or better suggestion: Yast XEN or firewall part should modify FW_FORWARD_ALWAYS_INOUT_DEV if firewall is active. -- 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=205092 ------- Comment #9 from Wojciech.Szenajch@bull.com.pl 2006-10-02 08:38 MST ------- Also suggested in README.SuSE enabling IP_FORWARD in /etc/sysconfig/sysctl was not required. On my both machines current value is: IP_FORWARD="no". -- 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=205092 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #10 from kallan@novell.com 2006-10-09 10:37 MST ------- The README.SuSE has been updated to reflect the current mechanism to enable the firewall to work with Xen bridging. Also, when installing Xen on SLES 10 or openSUSE 10.2 via YaST, SuSEfirewall2 is automatically updated to include FW_FORWARD_ALWAYS_INOUT_DEV=”xenbr0”. -- 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