I''m proposing to checkin the attached new /etc/xen/network script. I''m hoping it will be more robust to the various network startup problems people have seen by using vendor ifup/ifdown scripts. Please can people try it out, particularly if you had problems with the old script. If the script does fail for you, /var/log/xend.debug may have some useful info. Please try to dig around to try and understand what has gone wrong. I''ve attached the output of ifconfig before and after starting xend for comparison. We''re still awaiting patches to enable interfaces other than eth0 to be specified in xend-config.sxp, so if you''re primary interface is eth1 edit the default ''netdev'' parameter at the top of the file. Thanks, Ian *** BEFORE: eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 inet addr:108.32.38.50 Bcast:128.232.47.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:85 errors:0 dropped:0 overruns:0 frame:0 TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7868 (7.6 Kb) TX bytes:8233 (8.0 Kb) Interrupt:28 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2392 (2.3 Kb) TX bytes:2392 (2.3 Kb) *** AFTER: eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 inet addr:108.32.38.50 Bcast:128.232.47.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1689 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:118661 (115.8 Kb) TX bytes:969 (969.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2486 (2.4 Kb) TX bytes:2486 (2.4 Kb) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:1757 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:131689 (128.6 Kb) TX bytes:1003 (1003.0 b) Interrupt:28 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:1689 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:969 (969.0 b) TX bytes:118661 (115.8 Kb) xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1687 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:94164 (91.9 Kb) TX bytes:0 (0.0 b) # brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.feffffffffff no vif0.0 peth0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I tried the new network script on a couple of my boxes. I got it working fine with RHEL4 box (x86-32). But somehow it did not work for my SLES9 SP2 boxes (x86-32 and x85-64). The output of ifconfig on RHEL4 box looks right to me. But the ones on SLES9 SP2 does not. Here are the steps I used and how they looked like: 1) Right after I start xend: bl2-1:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5309 errors:0 dropped:0 overruns:0 frame:0 TX packets:1163 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:688727 (672.5 Kb) TX bytes:192155 (187.6 Kb) Interrupt:78 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX bytes:1620 (1.5 Kb) xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) 2) Right after I issued command "xm create vm1", it became: bl2-1:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5599 errors:0 dropped:0 overruns:0 frame:0 TX packets:1277 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:720829 (703.9 Kb) TX bytes:220263 (215.1 Kb) Interrupt:78 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX bytes:1620 (1.5 Kb) vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 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:84 (84.0 b) TX bytes:0 (0.0 b) xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 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:56 (56.0 b) TX bytes:0 (0.0 b) 3) The network was not pingable on domU after domU booted up. 4) Then I shutdown domU, and the output of ifconfig on domU went back to 1) 5) If I switch back to the old network script, network works fine on both dom0 and domU. Could this have something to do with the bridge-utils-0.9.6-121.1 which SLES9 SP2 uses? Li "Ian Pratt" <m+Ian.Pratt@cl.c am.ac.uk> To Sent by: "xen-devel" xen-devel-bounces <xen-devel@lists.xensource.com> @lists.xensource. cc com Subject [Xen-devel] new /etc/xen/network 08/09/2005 07:58 script PM I''m proposing to checkin the attached new /etc/xen/network script. I''m hoping it will be more robust to the various network startup problems people have seen by using vendor ifup/ifdown scripts. Please can people try it out, particularly if you had problems with the old script. If the script does fail for you, /var/log/xend.debug may have some useful info. Please try to dig around to try and understand what has gone wrong. I''ve attached the output of ifconfig before and after starting xend for comparison. We''re still awaiting patches to enable interfaces other than eth0 to be specified in xend-config.sxp, so if you''re primary interface is eth1 edit the default ''netdev'' parameter at the top of the file. Thanks, Ian *** BEFORE: eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 inet addr:108.32.38.50 Bcast:128.232.47.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:85 errors:0 dropped:0 overruns:0 frame:0 TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7868 (7.6 Kb) TX bytes:8233 (8.0 Kb) Interrupt:28 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2392 (2.3 Kb) TX bytes:2392 (2.3 Kb) *** AFTER: eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 inet addr:108.32.38.50 Bcast:128.232.47.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1689 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:118661 (115.8 Kb) TX bytes:969 (969.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2486 (2.4 Kb) TX bytes:2486 (2.4 Kb) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:1757 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:131689 (128.6 Kb) TX bytes:1003 (1003.0 b) Interrupt:28 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:1689 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:969 (969.0 b) TX bytes:118661 (115.8 Kb) xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1687 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:94164 (91.9 Kb) TX bytes:0 (0.0 b) # brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.feffffffffff no vif0.0 peth0 (See attached file: network)_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> I tried the new network script on a couple of my boxes. I got > it working fine with RHEL4 box (x86-32). But somehow it did > not work for my SLES9 SP2 boxes (x86-32 and x85-64). The > output of ifconfig on RHEL4 box looks right to me. But the > ones on SLES9 SP2 does not. Here are the steps I used and how > they looked like: > > 1) Right after I start xend:Do you still have network connectivity in dom0 after starting xend? Please post the output of the following commands before and after starting xend: ifconfig brctl show I see your setup has an eth1. Does it also have an eth0? Which do you want on xen-br0? Have you edited the default netdev line at the top of the new network script? Thanks, Ian> bl2-1:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5309 > errors:0 dropped:0 overruns:0 frame:0 TX packets:1163 > errors:0 dropped:0 overruns:0 carrier:0 collisions:0 > txqueuelen:1000 RX bytes:688727 (672.5 Kb) TX bytes:192155 (187.6 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX > packets:20 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX > bytes:1620 (1.5 Kb) > > xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 > 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:0 (0.0 b) TX bytes:0 (0.0 b) > > 2) Right after I issued command "xm create vm1", it became: > > bl2-1:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5599 > errors:0 dropped:0 overruns:0 frame:0 TX packets:1277 > errors:0 dropped:0 overruns:0 carrier:0 collisions:0 > txqueuelen:1000 RX bytes:720829 (703.9 Kb) TX bytes:220263 (215.1 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX > packets:20 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX > bytes:1620 (1.5 Kb) > > vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 > 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:84 (84.0 b) TX bytes:0 (0.0 b) > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 > 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:56 (56.0 b) TX bytes:0 (0.0 b) > > 3) The network was not pingable on domU after domU booted up. > > 4) Then I shutdown domU, and the output of ifconfig on domU > went back to 1) > > 5) If I switch back to the old network script, network works > fine on both dom0 and domU. > > Could this have something to do with the > bridge-utils-0.9.6-121.1 which SLES9 SP2 uses? > > > Li > > > Inactive hide details for "Ian Pratt" > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > Sent by: > xen-devel-bounces@lists.xensource.com > > 08/09/2005 07:58 PM > > > > To > > "xen-devel" <xen-devel@lists.xensource.com> > > > cc > > > > > Subject > > [Xen-devel] new /etc/xen/network script > > > > > I''m proposing to checkin the attached new /etc/xen/network > script. I''m hoping it will be more robust to the various > network startup problems people have seen by using vendor > ifup/ifdown scripts. > > Please can people try it out, particularly if you had > problems with the old script. > > If the script does fail for you, /var/log/xend.debug may have > some useful info. Please try to dig around to try and > understand what has gone wrong. I''ve attached the output of > ifconfig before and after starting xend for comparison. > > We''re still awaiting patches to enable interfaces other than > eth0 to be specified in xend-config.sxp, so if you''re primary > interface is eth1 edit the default ''netdev'' parameter at the > top of the file. > > Thanks, > Ian > > *** BEFORE: > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > inet addr:108.32.38.50 Bcast:128.232.47.255 > Mask:255.255.240.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:85 errors:0 dropped:0 overruns:0 frame:0 > TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:7868 (7.6 Kb) TX bytes:8233 (8.0 Kb) > Interrupt:28 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2392 (2.3 Kb) TX bytes:2392 (2.3 Kb) > > > > *** AFTER: > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > inet addr:108.32.38.50 Bcast:128.232.47.255 > Mask:255.255.240.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1689 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:118661 (115.8 Kb) TX bytes:969 (969.0 b) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:29 errors:0 dropped:0 overruns:0 frame:0 > TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2486 (2.4 Kb) TX bytes:2486 (2.4 Kb) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:1757 errors:0 dropped:0 overruns:0 frame:0 > TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:131689 (128.6 Kb) TX bytes:1003 (1003.0 b) > Interrupt:28 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:16 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1689 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:969 (969.0 b) TX bytes:118661 (115.8 Kb) > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1687 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:94164 (91.9 Kb) TX bytes:0 (0.0 b) > > > # brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.feffffffffff no vif0.0 > peth0 > > (See attached file: > network)_______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
My bl2-1 box is experiencing bug 62 again with today''s build. So I am just going to post output I get from another identical machine: Before starting xend: bl2-2:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1472 errors:0 dropped:0 overruns:0 frame:0 TX packets:289 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196472 (191.8 Kb) TX bytes:41347 (40.3 Kb) Interrupt:78 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX bytes:1512 (1.4 Kb) bl2-2:~ # brctl show bridge name bridge id STP enabled interfaces After starting xend: ( ifconfig output is not the same I saw yesterday...) bl2-2:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2260 errors:0 dropped:0 overruns:0 frame:0 TX packets:385 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:297268 (290.3 Kb) TX bytes:56563 (55.2 Kb) Interrupt:78 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX bytes:1512 (1.4 Kb) bl2-2:~ # brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.000000000000 no Both this two machines are IBM blades. Eth1 is used for network connection and eth0 is used for SOL (Serial Over LAN) connection on these blades. I did change eth0 to eth0 in network script. I will try to collect more info on non-blade box using eth0 later. Li "Ian Pratt" <m+Ian.Pratt@cl.c am.ac.uk> To Li Ge/Austin/IBM@IBMUS 08/11/2005 04:27 cc AM "xen-devel" <xen-devel@lists.xensource.com>, <xen-devel-bounces@lists.xensource. com>, <ian.pratt@cl.cam.ac.uk> Subject RE: [Xen-devel] new /etc/xen/network script> I tried the new network script on a couple of my boxes. I got > it working fine with RHEL4 box (x86-32). But somehow it did > not work for my SLES9 SP2 boxes (x86-32 and x85-64). The > output of ifconfig on RHEL4 box looks right to me. But the > ones on SLES9 SP2 does not. Here are the steps I used and how > they looked like: > > 1) Right after I start xend:Do you still have network connectivity in dom0 after starting xend? Please post the output of the following commands before and after starting xend: ifconfig brctl show I see your setup has an eth1. Does it also have an eth0? Which do you want on xen-br0? Have you edited the default netdev line at the top of the new network script? Thanks, Ian> bl2-1:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5309 > errors:0 dropped:0 overruns:0 frame:0 TX packets:1163 > errors:0 dropped:0 overruns:0 carrier:0 collisions:0 > txqueuelen:1000 RX bytes:688727 (672.5 Kb) TX bytes:192155 (187.6 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX > packets:20 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX > bytes:1620 (1.5 Kb) > > xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 > 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:0 (0.0 b) TX bytes:0 (0.0 b) > > 2) Right after I issued command "xm create vm1", it became: > > bl2-1:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5599 > errors:0 dropped:0 overruns:0 frame:0 TX packets:1277 > errors:0 dropped:0 overruns:0 carrier:0 collisions:0 > txqueuelen:1000 RX bytes:720829 (703.9 Kb) TX bytes:220263 (215.1 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX > packets:20 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX > bytes:1620 (1.5 Kb) > > vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 > 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:84 (84.0 b) TX bytes:0 (0.0 b) > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 > 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:56 (56.0 b) TX bytes:0 (0.0 b) > > 3) The network was not pingable on domU after domU booted up. > > 4) Then I shutdown domU, and the output of ifconfig on domU > went back to 1) > > 5) If I switch back to the old network script, network works > fine on both dom0 and domU. > > Could this have something to do with the > bridge-utils-0.9.6-121.1 which SLES9 SP2 uses? > > > Li > > > Inactive hide details for "Ian Pratt" > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > > > "Ian Pratt"<m+Ian.Pratt@cl.cam.ac.uk>> Sent by: > xen-devel-bounces@lists.xensource.com > > 08/09/2005 07:58 PM > > > > To > > "xen-devel" <xen-devel@lists.xensource.com> > > > cc > > > > > Subject > > [Xen-devel] new /etc/xen/network script > > > > > I''m proposing to checkin the attached new /etc/xen/network > script. I''m hoping it will be more robust to the various > network startup problems people have seen by using vendor > ifup/ifdown scripts. > > Please can people try it out, particularly if you had > problems with the old script. > > If the script does fail for you, /var/log/xend.debug may have > some useful info. Please try to dig around to try and > understand what has gone wrong. I''ve attached the output of > ifconfig before and after starting xend for comparison. > > We''re still awaiting patches to enable interfaces other than > eth0 to be specified in xend-config.sxp, so if you''re primary > interface is eth1 edit the default ''netdev'' parameter at the > top of the file. > > Thanks, > Ian > > *** BEFORE: > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > inet addr:108.32.38.50 Bcast:128.232.47.255 > Mask:255.255.240.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:85 errors:0 dropped:0 overruns:0 frame:0 > TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:7868 (7.6 Kb) TX bytes:8233 (8.0 Kb) > Interrupt:28 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2392 (2.3 Kb) TX bytes:2392 (2.3 Kb) > > > > *** AFTER: > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > inet addr:108.32.38.50 Bcast:128.232.47.255 > Mask:255.255.240.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1689 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:118661 (115.8 Kb) TX bytes:969 (969.0 b) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:29 errors:0 dropped:0 overruns:0 frame:0 > TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2486 (2.4 Kb) TX bytes:2486 (2.4 Kb) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:1757 errors:0 dropped:0 overruns:0 frame:0 > TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:131689 (128.6 Kb) TX bytes:1003 (1003.0 b) > Interrupt:28 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:16 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1689 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:969 (969.0 b) TX bytes:118661 (115.8 Kb) > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1687 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:94164 (91.9 Kb) TX bytes:0 (0.0 b) > > > # brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.feffffffffff no vif0.0 > peth0 > > (See attached file: > network)_______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
More information I gathered on a box(SLES9 SP2) using eth0: Before starting xend: x235:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:436 errors:0 dropped:0 overruns:0 frame:0 TX packets:167 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:69197 (67.5 Kb) TX bytes:20897 (20.4 Kb) Interrupt:29 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX bytes:2880 (2.8 Kb) x235:~ # brctl show bridge name bridge id STP enabled interfaces After starting xend: x235:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:662 errors:0 dropped:0 overruns:0 frame:0 TX packets:220 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:99481 (97.1 Kb) TX bytes:30399 (29.6 Kb) Interrupt:29 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX bytes:2880 (2.8 Kb) xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) x235:~ # brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.000000000000 no I still have network connectivity in dom0 after starting xend. Thanks, Li Li Ge/Austin/IBM@IBM US To Sent by: "Ian Pratt" xen-devel-bounces <m+Ian.Pratt@cl.cam.ac.uk> @lists.xensource. cc com xen-devel <xen-devel@lists.xensource.com>, xen-devel-bounces@lists.xensource.c 08/11/2005 12:36 om PM Subject RE: [Xen-devel] new /etc/xen/network script My bl2-1 box is experiencing bug 62 again with today''s build. So I am just going to post output I get from another identical machine: Before starting xend: bl2-2:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1472 errors:0 dropped:0 overruns:0 frame:0 TX packets:289 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196472 (191.8 Kb) TX bytes:41347 (40.3 Kb) Interrupt:78 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX bytes:1512 (1.4 Kb) bl2-2:~ # brctl show bridge name bridge id STP enabled interfaces After starting xend: ( ifconfig output is not the same I saw yesterday...) bl2-2:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2260 errors:0 dropped:0 overruns:0 frame:0 TX packets:385 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:297268 (290.3 Kb) TX bytes:56563 (55.2 Kb) Interrupt:78 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX bytes:1512 (1.4 Kb) bl2-2:~ # brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.000000000000 no Both this two machines are IBM blades. Eth1 is used for network connection and eth0 is used for SOL (Serial Over LAN) connection on these blades. I did change eth0 to eth0 in network script. I will try to collect more info on non-blade box using eth0 later. Li Inactive hide details for "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> "Ian Pratt" <m+Ian.Pra tt@cl.cam. ac.uk> To Li Ge/Austin/IBM@IBMUS 08/11/2005 04:27 AM cc "xen-devel" <xen-devel@lists.xensource.com >, <xen-devel-bounces@lists.xenso urce.com>, <ian.pratt@cl.cam.ac.uk> Subject RE: [Xen-devel] new /etc/xen/network script> I tried the new network script on a couple of my boxes. I got > it working fine with RHEL4 box (x86-32). But somehow it did > not work for my SLES9 SP2 boxes (x86-32 and x85-64). The > output of ifconfig on RHEL4 box looks right to me. But the > ones on SLES9 SP2 does not. Here are the steps I used and how > they looked like: > > 1) Right after I start xend:Do you still have network connectivity in dom0 after starting xend? Please post the output of the following commands before and after starting xend: ifconfig brctl show I see your setup has an eth1. Does it also have an eth0? Which do you want on xen-br0? Have you edited the default netdev line at the top of the new network script? Thanks, Ian> bl2-1:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5309 > errors:0 dropped:0 overruns:0 frame:0 TX packets:1163 > errors:0 dropped:0 overruns:0 carrier:0 collisions:0 > txqueuelen:1000 RX bytes:688727 (672.5 Kb) TX bytes:192155 (187.6 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX > packets:20 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX > bytes:1620 (1.5 Kb) > > xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 > 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:0 (0.0 b) TX bytes:0 (0.0 b) > > 2) Right after I issued command "xm create vm1", it became: > > bl2-1:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5599 > errors:0 dropped:0 overruns:0 frame:0 TX packets:1277 > errors:0 dropped:0 overruns:0 carrier:0 collisions:0 > txqueuelen:1000 RX bytes:720829 (703.9 Kb) TX bytes:220263 (215.1 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX > packets:20 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1620 (1.5 Kb) TX > bytes:1620 (1.5 Kb) > > vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 > 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:84 (84.0 b) TX bytes:0 (0.0 b) > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 > 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:56 (56.0 b) TX bytes:0 (0.0 b) > > 3) The network was not pingable on domU after domU booted up. > > 4) Then I shutdown domU, and the output of ifconfig on domU > went back to 1) > > 5) If I switch back to the old network script, network works > fine on both dom0 and domU. > > Could this have something to do with the > bridge-utils-0.9.6-121.1 which SLES9 SP2 uses? > > > Li > > > Inactive hide details for "Ian Pratt" > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > Sent by: > xen-devel-bounces@lists.xensource.com > > 08/09/2005 07:58 PM > > > > To > > "xen-devel" <xen-devel@lists.xensource.com> > > > cc > > > > > Subject > > [Xen-devel] new /etc/xen/network script > > > > > I''m proposing to checkin the attached new /etc/xen/network > script. I''m hoping it will be more robust to the various > network startup problems people have seen by using vendor > ifup/ifdown scripts. > > Please can people try it out, particularly if you had > problems with the old script. > > If the script does fail for you, /var/log/xend.debug may have > some useful info. Please try to dig around to try and > understand what has gone wrong. I''ve attached the output of > ifconfig before and after starting xend for comparison. > > We''re still awaiting patches to enable interfaces other than > eth0 to be specified in xend-config.sxp, so if you''re primary > interface is eth1 edit the default ''netdev'' parameter at the > top of the file. > > Thanks, > Ian > > *** BEFORE: > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > inet addr:108.32.38.50 Bcast:128.232.47.255 > Mask:255.255.240.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:85 errors:0 dropped:0 overruns:0 frame:0 > TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:7868 (7.6 Kb) TX bytes:8233 (8.0 Kb) > Interrupt:28 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2392 (2.3 Kb) TX bytes:2392 (2.3 Kb) > > > > *** AFTER: > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > inet addr:108.32.38.50 Bcast:128.232.47.255 > Mask:255.255.240.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1689 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:118661 (115.8 Kb) TX bytes:969 (969.0 b) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:29 errors:0 dropped:0 overruns:0 frame:0 > TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2486 (2.4 Kb) TX bytes:2486 (2.4 Kb) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:1757 errors:0 dropped:0 overruns:0 frame:0 > TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:131689 (128.6 Kb) TX bytes:1003 (1003.0 b) > Interrupt:28 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:16 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1689 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:969 (969.0 b) TX bytes:118661 (115.8 Kb) > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1687 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:94164 (91.9 Kb) TX bytes:0 (0.0 b) > > > # brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.feffffffffff no vif0.0 > peth0 > > (See attached file: > network)_______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> More information I gathered on a box(SLES9 SP2) using eth0:On the machine with eth0, please send the relevant bit of /var/log/xend.log Also, what happens if you do: ifdown eth0 ifup eth0 Thanks, Ian> Before starting xend: > > x235:~ # ifconfig > eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet > addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:436 > errors:0 dropped:0 overruns:0 frame:0 TX packets:167 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:69197 (67.5 Kb) TX bytes:20897 (20.4 Kb) > Interrupt:29 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX > packets:36 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX > bytes:2880 (2.8 Kb) > > x235:~ # brctl show > bridge name bridge id STP enabled interfaces > > After starting xend: > > x235:~ # ifconfig > eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet > addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:662 > errors:0 dropped:0 overruns:0 frame:0 TX packets:220 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:99481 (97.1 Kb) TX bytes:30399 (29.6 Kb) > Interrupt:29 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX > packets:36 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX > bytes:2880 (2.8 Kb) > > xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 > 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:0 (0.0 b) TX bytes:0 (0.0 b) x235:~ # brctl show bridge > name bridge id STP enabled interfaces xen-br0 8000.000000000000 no > > I still have network connectivity in dom0 after starting xend. > > Thanks, > Li > > Inactive hide details for Li Ge/Austin/IBM@IBMUSLi Ge/Austin/IBM@IBMUS > > > > > Li Ge/Austin/IBM@IBMUS > Sent by: > xen-devel-bounces@lists.xensource.com > > 08/11/2005 12:36 PM > > > > To > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > cc > > xen-devel <xen-devel@lists.xensource.com>, > xen-devel-bounces@lists.xensource.com > > > Subject > > RE: [Xen-devel] new /etc/xen/network script > > > My bl2-1 box is experiencing bug 62 again with today''s build. > So I am just going to post output I get from another > identical machine: > > Before starting xend: > bl2-2:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet > addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1472 > errors:0 dropped:0 overruns:0 frame:0 TX packets:289 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:196472 (191.8 Kb) TX bytes:41347 (40.3 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX > packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX > bytes:1512 (1.4 Kb) bl2-2:~ # brctl show bridge name bridge > id STP enabled interfaces > > After starting xend: ( ifconfig output is not the same I saw > yesterday...) > > bl2-2:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet > addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2260 > errors:0 dropped:0 overruns:0 frame:0 TX packets:385 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:297268 (290.3 Kb) TX bytes:56563 (55.2 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX > packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX > bytes:1512 (1.4 Kb) > > bl2-2:~ # brctl show > bridge name bridge id STP enabled interfaces xen-br0 > 8000.000000000000 no > > > Both this two machines are IBM blades. Eth1 is used for > network connection and eth0 is used for SOL (Serial Over LAN) > connection on these blades. I did change eth0 to eth0 in > network script. > > I will try to collect more info on non-blade box using eth0 later. > > Li > > Inactive hide details for "Ian Pratt" > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > 08/11/2005 04:27 AM > > > To > > Li Ge/Austin/IBM@IBMUS > > cc > > "xen-devel" <xen-devel@lists.xensource.com>, > <xen-devel-bounces@lists.xensource.com>, <ian.pratt@cl.cam.ac.uk> > > Subject > > RE: [Xen-devel] new /etc/xen/network script > > > > > I tried the new network script on a couple of my boxes. I got it > > working fine with RHEL4 box (x86-32). But somehow it did > not work for > > my SLES9 SP2 boxes (x86-32 and x85-64). The output of ifconfig on > > RHEL4 box looks right to me. But the ones on SLES9 SP2 does > not. Here > > are the steps I used and how they looked like: > > > > 1) Right after I start xend: > > Do you still have network connectivity in dom0 after starting xend? > > Please post the output of the following commands before and > after starting xend: > > ifconfig > brctl show > > I see your setup has an eth1. Does it also have an eth0? > Which do you want on xen-br0? Have you edited the default > netdev line at the top of the new network script? > > Thanks, > Ian > > > bl2-1:~ # ifconfig > > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5309 > errors:0 dropped:0 > > overruns:0 frame:0 TX packets:1163 errors:0 dropped:0 overruns:0 > > carrier:0 collisions:0 txqueuelen:1000 RX bytes:688727 > (672.5 Kb) TX > > bytes:192155 (187.6 Kb) > > Interrupt:78 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 > > dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 > > overruns:0 carrier:0 collisions:0 txqueuelen:0 RX > bytes:1620 (1.5 Kb) > > TX bytes:1620 (1.5 Kb) > > > > xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX > bytes:0 (0.0 > > b) > > > > 2) Right after I issued command "xm create vm1", it became: > > > > bl2-1:~ # ifconfig > > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5599 > errors:0 dropped:0 > > overruns:0 frame:0 TX packets:1277 errors:0 dropped:0 overruns:0 > > carrier:0 collisions:0 txqueuelen:1000 RX bytes:720829 > (703.9 Kb) TX > > bytes:220263 (215.1 Kb) > > Interrupt:78 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 > > dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 > > overruns:0 carrier:0 collisions:0 txqueuelen:0 RX > bytes:1620 (1.5 Kb) > > TX bytes:1620 (1.5 Kb) > > > > vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 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:84 (84.0 b) TX bytes:0 (0.0 b) > > > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 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:56 (56.0 b) TX bytes:0 (0.0 b) > > > > 3) The network was not pingable on domU after domU booted up. > > > > 4) Then I shutdown domU, and the output of ifconfig on domU > went back > > to 1) > > > > 5) If I switch back to the old network script, network > works fine on > > both dom0 and domU. > > > > Could this have something to do with the > > bridge-utils-0.9.6-121.1 which SLES9 SP2 uses? > > > > > > Li > > > > > > Inactive hide details for "Ian Pratt" > > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > > > > > > > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> Sent by: > > xen-devel-bounces@lists.xensource.com > > > > 08/09/2005 07:58 PM > > > > > > > > To > > > > "xen-devel" <xen-devel@lists.xensource.com> > > > > > > cc > > > > > > > > > > Subject > > > > [Xen-devel] new /etc/xen/network script > > > > > > > > > > I''m proposing to checkin the attached new /etc/xen/network > script. I''m > > hoping it will be more robust to the various network > startup problems > > people have seen by using vendor ifup/ifdown scripts. > > > > Please can people try it out, particularly if you had problems with > > the old script. > > > > If the script does fail for you, /var/log/xend.debug may have some > > useful info. Please try to dig around to try and understand > what has > > gone wrong. I''ve attached the output of ifconfig before and after > > starting xend for comparison. > > > > We''re still awaiting patches to enable interfaces other > than eth0 to > > be specified in xend-config.sxp, so if you''re primary interface is > > eth1 edit the default ''netdev'' parameter at the top of the file. > > > > Thanks, > > Ian > > > > *** BEFORE: > > > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > > inet addr:108.32.38.50 Bcast:128.232.47.255 > > Mask:255.255.240.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:85 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:7868 (7.6 Kb) TX bytes:8233 (8.0 Kb) > > Interrupt:28 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:2392 (2.3 Kb) TX bytes:2392 (2.3 Kb) > > > > > > > > *** AFTER: > > > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > > inet addr:108.32.38.50 Bcast:128.232.47.255 > > Mask:255.255.240.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:1689 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:118661 (115.8 Kb) TX bytes:969 (969.0 b) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:29 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:2486 (2.4 Kb) TX bytes:2486 (2.4 Kb) > > > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > > RX packets:1757 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:131689 (128.6 Kb) TX bytes:1003 (1003.0 b) > > Interrupt:28 > > > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:16 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1689 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:969 (969.0 b) TX bytes:118661 (115.8 Kb) > > > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:1687 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:94164 (91.9 Kb) TX bytes:0 (0.0 b) > > > > > > # brctl show > > bridge name bridge id STP enabled interfaces > > xen-br0 8000.feffffffffff no vif0.0 > > peth0 > > > > (See attached file: > > network)_______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > <http://lists.xensource.com/xen-devel> > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
/var/log/xend.log [1970-08-11 11:42:12 xend] INFO (XendRoot:141) EVENT> xend.virq 3 [1970-08-11 12:37:38 xend] INFO (SrvDaemon:300) Xend Daemon started [1970-08-11 12:37:38 xend] INFO (channel:163) Virq 3 on port 14 [1970-08-11 12:37:38 xend] DEBUG (XendDomainInfo:178) info={''vcpu_to_cpu'': [0, - 1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, - 1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1], ''cpu_time'': 36462215182L, ''ssidref'': 0, ''shutdown_reason'': 0, ''dying'': 0, ''dom'': 0, ''running'': 1, ''maxmem_kb'': -4, '' paused'': 0, ''crashed'': 0, ''vcpus'': 1, ''shutdown'': 0, ''mem_kb'': 250880, ''cpumap'': [-1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], ''blocked'': 0} [1970-08-11 12:37:38 xend] DEBUG (XendDomainInfo:179) config=''None'' [1970-08-11 12:37:38 xend] INFO (xsobj:326) DBMap>introduceDomain> 0 43421 <Even tChannel dom1:0:15 dom2:0:16> /domain/5c25e1eb-75fc-4b63-879a-79e0f25cc3a7 [1970-08-11 12:37:38 xend] DEBUG (XendDomainInfo:564) writing key online=1 to pa th /cpus/cpu0 in store [1970-08-11 12:37:38 xend] INFO (SrvServer:78) unix path=/var/lib/xend/xend-sock et [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + set -e [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + OP=start [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + shift [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + export bridge=xen-br0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + bridge=xen-br0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + export antispoof=no [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + antispoof=no [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + bridge=xen-br0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + netdev=eth0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + antispoof=no [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + echo ''*network start b ridge=xen-br0 netdev=eth0 antispoof=no'' [1970-08-11 12:37:38 xend] INFO (process:35) [network] network start bridge=xen- br0 netdev=eth0 antispoof=no [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + op_start [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + ''['' xen-br0 =null ''] '' [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + create_bridge xen-br0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + local bridge=xen-br0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + brctl show [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + grep -q xen-br0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + brctl addbr xen-br0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + brctl stp xen-br0 off [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + brctl setfd xen-br0 0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + ifconfig xen-br0 up [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + ifconfig [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + grep -q veth0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + ifconfig veth0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + grep -q veth0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] ++ ifconfig eth0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] ++ grep HWadd [1970-08-11 12:37:38 xend] INFO (XendRoot:141) EVENT> xend.start 0 [1970-08-11 12:37:38 xend] ERROR (process:37) [network] ++ sed -e ''s/.*\(..:..:. .:..:..:..\).*/\1/'' [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + mac=00:09:6B:A5:B5:EE [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + ifdown eth0 '']'' Please ignore the timestamp in the log. There was a timing issue. I changed MMDDhhmm but forgot to change YY. After "ifdown eth0": x235:~ # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 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:5968 (5.8 Kb) TX bytes:5968 (5.8 Kb) xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) "ifup eth0": x235:~ # ifup eth0 eth0 device: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) eth0 configuration: eth-id-00:09:6b:a5:b5:ee x235:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:29 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 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:5968 (5.8 Kb) TX bytes:5968 (5.8 Kb) xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) The network comes back and works fine on dom0. Thanks, Li "Ian Pratt" <m+Ian.Pratt@cl.c am.ac.uk> To Sent by: Li Ge/Austin/IBM@IBMUS xen-devel-bounces cc @lists.xensource. xen-devel com <xen-devel@lists.xensource.com>, xen-devel-bounces@lists.xensource.c om 08/11/2005 02:16 Subject PM RE: [Xen-devel] new /etc/xen/network script> More information I gathered on a box(SLES9 SP2) using eth0:On the machine with eth0, please send the relevant bit of /var/log/xend.log Also, what happens if you do: ifdown eth0 ifup eth0 Thanks, Ian> Before starting xend: > > x235:~ # ifconfig > eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet > addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:436 > errors:0 dropped:0 overruns:0 frame:0 TX packets:167 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:69197 (67.5 Kb) TX bytes:20897 (20.4 Kb) > Interrupt:29 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX > packets:36 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX > bytes:2880 (2.8 Kb) > > x235:~ # brctl show > bridge name bridge id STP enabled interfaces > > After starting xend: > > x235:~ # ifconfig > eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet > addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:662 > errors:0 dropped:0 overruns:0 frame:0 TX packets:220 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:99481 (97.1 Kb) TX bytes:30399 (29.6 Kb) > Interrupt:29 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX > packets:36 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX > bytes:2880 (2.8 Kb) > > xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 > 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:0 (0.0 b) TX bytes:0 (0.0 b) x235:~ # brctl show bridge > name bridge id STP enabled interfaces xen-br0 8000.000000000000 no > > I still have network connectivity in dom0 after starting xend. > > Thanks, > Li > > Inactive hide details for Li Ge/Austin/IBM@IBMUSLi Ge/Austin/IBM@IBMUS > > > > > Li Ge/Austin/IBM@IBMUS > Sent by: > xen-devel-bounces@lists.xensource.com > > 08/11/2005 12:36 PM > > > > To > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > cc > > xen-devel <xen-devel@lists.xensource.com>, > xen-devel-bounces@lists.xensource.com > > > Subject > > RE: [Xen-devel] new /etc/xen/network script > > > My bl2-1 box is experiencing bug 62 again with today''s build. > So I am just going to post output I get from another > identical machine: > > Before starting xend: > bl2-2:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet > addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1472 > errors:0 dropped:0 overruns:0 frame:0 TX packets:289 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:196472 (191.8 Kb) TX bytes:41347 (40.3 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX > packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX > bytes:1512 (1.4 Kb) bl2-2:~ # brctl show bridge name bridge > id STP enabled interfaces > > After starting xend: ( ifconfig output is not the same I saw > yesterday...) > > bl2-2:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:63:19 inet > addr:9.3.192.195 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2260 > errors:0 dropped:0 overruns:0 frame:0 TX packets:385 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:297268 (290.3 Kb) TX bytes:56563 (55.2 Kb) > Interrupt:78 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX > packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX > bytes:1512 (1.4 Kb) > > bl2-2:~ # brctl show > bridge name bridge id STP enabled interfaces xen-br0 > 8000.000000000000 no > > > Both this two machines are IBM blades. Eth1 is used for > network connection and eth0 is used for SOL (Serial Over LAN) > connection on these blades. I did change eth0 to eth0 in > network script. > > I will try to collect more info on non-blade box using eth0 later. > > Li > > Inactive hide details for "Ian Pratt" > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > >> "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > >> 08/11/2005 04:27 AM > > > To > > Li Ge/Austin/IBM@IBMUS > > cc > > "xen-devel" <xen-devel@lists.xensource.com>, > <xen-devel-bounces@lists.xensource.com>, <ian.pratt@cl.cam.ac.uk>> > Subject > > RE: [Xen-devel] new /etc/xen/network script > > > > > I tried the new network script on a couple of my boxes. I got it > > working fine with RHEL4 box (x86-32). But somehow it did > not work for > > my SLES9 SP2 boxes (x86-32 and x85-64). The output of ifconfig on > > RHEL4 box looks right to me. But the ones on SLES9 SP2 does > not. Here > > are the steps I used and how they looked like: > > > > 1) Right after I start xend: > > Do you still have network connectivity in dom0 after starting xend? > > Please post the output of the following commands before and > after starting xend: > > ifconfig > brctl show > > I see your setup has an eth1. Does it also have an eth0? > Which do you want on xen-br0? Have you edited the default > netdev line at the top of the new network script? > > Thanks, > Ian > > > bl2-1:~ # ifconfig > > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5309 > errors:0 dropped:0 > > overruns:0 frame:0 TX packets:1163 errors:0 dropped:0 overruns:0 > > carrier:0 collisions:0 txqueuelen:1000 RX bytes:688727 > (672.5 Kb) TX > > bytes:192155 (187.6 Kb) > > Interrupt:78 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 > > dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 > > overruns:0 carrier:0 collisions:0 txqueuelen:0 RX > bytes:1620 (1.5 Kb) > > TX bytes:1620 (1.5 Kb) > > > > xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX > bytes:0 (0.0 > > b) > > > > 2) Right after I issued command "xm create vm1", it became: > > > > bl2-1:~ # ifconfig > > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet > > addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5599 > errors:0 dropped:0 > > overruns:0 frame:0 TX packets:1277 errors:0 dropped:0 overruns:0 > > carrier:0 collisions:0 txqueuelen:1000 RX bytes:720829 > (703.9 Kb) TX > > bytes:220263 (215.1 Kb) > > Interrupt:78 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 > > dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 > > overruns:0 carrier:0 collisions:0 txqueuelen:0 RX > bytes:1620 (1.5 Kb) > > TX bytes:1620 (1.5 Kb) > > > > vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 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:84 (84.0 b) TX bytes:0 (0.0 b) > > > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST > > RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 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:56 (56.0 b) TX bytes:0 (0.0 b) > > > > 3) The network was not pingable on domU after domU booted up. > > > > 4) Then I shutdown domU, and the output of ifconfig on domU > went back > > to 1) > > > > 5) If I switch back to the old network script, network > works fine on > > both dom0 and domU. > > > > Could this have something to do with the > > bridge-utils-0.9.6-121.1 which SLES9 SP2 uses? > > > > > > Li > > > > > > Inactive hide details for "Ian Pratt" > > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > > > > > > > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> Sent by: > > xen-devel-bounces@lists.xensource.com > > > > 08/09/2005 07:58 PM > > > > > > > > To > > > > "xen-devel" <xen-devel@lists.xensource.com> > > > > > > cc > > > > > > > > > > Subject > > > > [Xen-devel] new /etc/xen/network script > > > > > > > > > > I''m proposing to checkin the attached new /etc/xen/network > script. I''m > > hoping it will be more robust to the various network > startup problems > > people have seen by using vendor ifup/ifdown scripts. > > > > Please can people try it out, particularly if you had problems with > > the old script. > > > > If the script does fail for you, /var/log/xend.debug may have some > > useful info. Please try to dig around to try and understand > what has > > gone wrong. I''ve attached the output of ifconfig before and after > > starting xend for comparison. > > > > We''re still awaiting patches to enable interfaces other > than eth0 to > > be specified in xend-config.sxp, so if you''re primary interface is > > eth1 edit the default ''netdev'' parameter at the top of the file. > > > > Thanks, > > Ian > > > > *** BEFORE: > > > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > > inet addr:108.32.38.50 Bcast:128.232.47.255 > > Mask:255.255.240.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:85 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:7868 (7.6 Kb) TX bytes:8233 (8.0 Kb) > > Interrupt:28 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:28 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:2392 (2.3 Kb) TX bytes:2392 (2.3 Kb) > > > > > > > > *** AFTER: > > > > eth0 Link encap:Ethernet HWaddr 00:06:5B:F6:90:B3 > > inet addr:108.32.38.50 Bcast:128.232.47.255 > > Mask:255.255.240.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:1689 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:118661 (115.8 Kb) TX bytes:969 (969.0 b) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:29 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:2486 (2.4 Kb) TX bytes:2486 (2.4 Kb) > > > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > > RX packets:1757 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:131689 (128.6 Kb) TX bytes:1003 (1003.0 b) > > Interrupt:28 > > > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:16 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1689 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:969 (969.0 b) TX bytes:118661 (115.8 Kb) > > > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:1687 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:94164 (91.9 Kb) TX bytes:0 (0.0 b) > > > > > > # brctl show > > bridge name bridge id STP enabled interfaces > > xen-br0 8000.feffffffffff no vif0.0 > > peth0 > > > > (See attached file: > > network)_______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > <http://lists.xensource.com/xen-devel> > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> > Please ignore the timestamp in the log. There was a timing > issue. I changed MMDDhhmm but forgot to change YY. > > After "ifdown eth0":Argghh. There''s a really stupid bug in the script. Please edit the following line: -if ! ifdown ${netdev} ] ; then +if ! ifdown ${netdev} ; then I''m not sure that the extraneous '']'' is actually the problem, though. Please can you add a `which ifdown` just before that line. Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ok, I modifed the script. Here is the new result: After I started xend, the network connection of dom0 lost. x235:/tmp # ifconfig eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:378 (378.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:81 errors:0 dropped:0 overruns:0 frame:0 TX packets:81 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6393 (6.2 Kb) TX bytes:6393 (6.2 Kb) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:964 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:94676 (92.4 Kb) TX bytes:0 (0.0 b) Interrupt:29 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9 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:378 (378.0 b) TX bytes:0 (0.0 b) x235:/var/log # ping 9.3.192.1 PING 9.3.192.1 (9.3.192.1) 56(84) bytes of data.>From 9.3.192.65: icmp_seq=1 Destination Host Unreachable >From 9.3.192.65 icmp_seq=1 Destination Host Unreachable >From 9.3.192.65 icmp_seq=2 Destination Host Unreachable >From 9.3.192.65 icmp_seq=3 Destination Host UnreachableI did "ifdown eth0" and "ifup eth0" here. Still the network did not come up. This is new log info from /var/log/xend.log: [1970-08-11 12:37:38 xend] ERROR (process:37) [network] + ifdown eth0 '']'' [1970-08-11 16:12:17 xend] INFO (SrvDaemon:300) Xend Daemon started [1970-08-11 16:12:18 xend] INFO (channel:163) Virq 3 on port 14 [1970-08-11 16:12:18 xend] DEBUG (XendDomainInfo:178) info={''vcpu_to_cpu'': [0, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1], ''cpu_time'': 35616069146L, ''ssidref'': 0, ''shutdown_reason'': 0, ''dying'': 0, ''dom'': 0, ''running'': 1, ''maxmem_kb'': -4, ''paused'': 0, ''crashed'': 0, ''vcpus'': 1, ''shutdown'': 0, ''mem_kb'': 250880, ''cpumap'': [-1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], ''blocked'': 0} [1970-08-11 16:12:18 xend] DEBUG (XendDomainInfo:179) config=''None'' [1970-08-11 16:12:18 xend] INFO (xsobj:326) DBMap>introduceDomain> 0 15447 <EventChannel dom1:0:15 dom2:0:16> /domain/5c25e1eb-75fc-4b63-879a-79e0f25cc3a7 [1970-08-11 16:12:18 xend] DEBUG (XendDomainInfo:564) writing key online=1 to path /cpus/cpu0 in store [1970-08-11 16:12:18 xend] INFO (SrvServer:78) unix path=/var/lib/xend/xend-socket [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + set -e [1970-08-11 16:12:18 xend] INFO (XendRoot:141) EVENT> xend.start 0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + OP=start [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + shift [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + export bridge=xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + bridge=xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + export antispoof=no [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + antispoof=no [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + bridge=xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + netdev=eth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + antispoof=no [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + echo ''*network start bridge=xen-br0 netdev=eth0 antispoof=no'' [1970-08-11 16:12:18 xend] INFO (process:35) [network] network start bridge=xen-br0 netdev=eth0 antispoof=no [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + op_start [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ''['' xen-br0 =null '']'' [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + create_bridge xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + local bridge=xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl show [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + grep -q xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl addbr xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl stp xen-br0 off [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl setfd xen-br0 0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifconfig xen-br0 up [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifconfig [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + grep -q veth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifconfig veth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + grep -q veth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] ++ ifconfig eth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] ++ grep HWadd [1970-08-11 16:12:18 xend] ERROR (process:37) [network] ++ sed -e ''s/.*\(..:..:..:..:..:..\).*/\1/'' [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + mac=00:09:6B:A5:B5:EE [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + which ifdown [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifdown eth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ip link set eth0 name peth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ip link set veth0 name eth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifconfig peth0 -arp down [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifconfig eth0 hw ether 00:09:6B:A5:B5:EE [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + add_to_bridge xen-br0 vif0.0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + local bridge=xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + local dev=vif0.0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl show [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + grep -q vif0.0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl addif xen-br0 vif0.0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + add_to_bridge xen-br0 peth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + local bridge=xen-br0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + local dev=peth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl show [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + grep -q peth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + brctl addif xen-br0 peth0 [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ip link set vif0.0 up [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ip link set peth0 up [1970-08-11 16:12:18 xend] ERROR (process:37) [network] + ifup eth0 Thanks, Li "Ian Pratt" <m+Ian.Pratt@cl.c am.ac.uk> To Li Ge/Austin/IBM@IBMUS 08/11/2005 03:52 cc PM "xen-devel" <xen-devel@lists.xensource.com>, <xen-devel-bounces@lists.xensource. com>, <ian.pratt@cl.cam.ac.uk> Subject RE: [Xen-devel] new /etc/xen/network script >> Please ignore the timestamp in the log. There was a timing > issue. I changed MMDDhhmm but forgot to change YY. > > After "ifdown eth0":Argghh. There''s a really stupid bug in the script. Please edit the following line: -if ! ifdown ${netdev} ] ; then +if ! ifdown ${netdev} ; then I''m not sure that the extraneous '']'' is actually the problem, though. Please can you add a `which ifdown` just before that line. Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Ok, I modifed the script. Here is the new result: > > After I started xend, the network connection of dom0 lost.OK, this is interesting. It''s the same symptoms as the old script. It looks like peth0 is receiving packets. Please confirm this with: tcpdump -i peth0 What''s odd is that there''s no xen-br0 showing up in ifconfig. I''d expect to see something like: xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:949 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:54097 (52.8 Kb) TX bytes:0 (0.0 b) Can you post the output of ''brctl show''. You should see: [root@commando-0 root]# brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.feffffffffff no vif0.0 peth0 Also, please can you try replacing the following lines: - add_to_bridge ${bridge} vif0.0 - add_to_bridge ${bridge} p${netdev} + brctl addif ${bridge} vif0.0 + brctl addif ${bridge} p${netdev} and earlier: + create_bridge ${bridge} - brctl addbr ${bridge} Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I modified the script based on what you suggested. Now after starting xend, there is nothing changed in the output of ifconfig: x235:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5356 errors:0 dropped:0 overruns:0 frame:0 TX packets:374 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:732337 (715.1 Kb) TX bytes:48514 (47.3 Kb) Interrupt:29 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX bytes:2880 (2.8 Kb) Also I can not even do xm list: x235:~ # ps -ef|grep xend root 22613 1 5 14:35 ? 00:00:00 python /usr/sbin/xend start root 22614 22613 0 14:35 pts/0 00:00:00 python /usr/sbin/xend start root 22615 22614 0 14:35 pts/0 00:00:00 python /usr/sbin/xend start root 22616 22614 0 14:35 pts/0 00:00:00 python /usr/sbin/xend start root 22617 22614 0 14:35 pts/0 00:00:00 python /usr/sbin/xend start root 22618 22614 0 14:35 pts/0 00:00:00 python /usr/sbin/xend start root 23070 10759 0 14:35 pts/0 00:00:00 grep xend x235:~ # xm list (111, ''Connection refused'') Error: Error connecting to xend, is xend running? Switching back to the original network script, the network works again. Not sure if I catched all the changes that you suggested. Here is the diff between the new network file you sent and my modified one: 123c123,124 < brctl addbr ${bridge} ---> #brctl addbr ${bridge} > create_bridge ${bridge}180c181,182 < if ! ifdown ${netdev} ] ; then ---> which ifdown > if ! ifdown ${netdev} ; then195,196c197,200 < add_to_bridge ${bridge} vif0.0 < add_to_bridge ${bridge} p${netdev} ---> #add_to_bridge ${bridge} vif0.0 > #add_to_bridge ${bridge} p${netdev} > brctl addif ${bridge} vif0.0 > brctl addif ${bridge} p${netdev}Li "Ian Pratt" <m+Ian.Pratt@cl.c am.ac.uk> To Li Ge/Austin/IBM@IBMUS 08/11/2005 05:17 cc PM <ian.pratt@cl.cam.ac.uk>, "xen-devel" <xen-devel@lists.xensource.com>, <xen-devel-bounces@lists.xensource. com>, <ian.pratt@cl.cam.ac.uk> Subject RE: [Xen-devel] new /etc/xen/network script> Ok, I modifed the script. Here is the new result: > > After I started xend, the network connection of dom0 lost.OK, this is interesting. It''s the same symptoms as the old script. It looks like peth0 is receiving packets. Please confirm this with: tcpdump -i peth0 What''s odd is that there''s no xen-br0 showing up in ifconfig. I''d expect to see something like: xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:949 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:54097 (52.8 Kb) TX bytes:0 (0.0 b) Can you post the output of ''brctl show''. You should see: [root@commando-0 root]# brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.feffffffffff no vif0.0 peth0 Also, please can you try replacing the following lines: - add_to_bridge ${bridge} vif0.0 - add_to_bridge ${bridge} p${netdev} + brctl addif ${bridge} vif0.0 + brctl addif ${bridge} p${netdev} and earlier: + create_bridge ${bridge} - brctl addbr ${bridge} Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> I modified the script based on what you suggested. Now after > starting xend, there is nothing changed in the output of ifconfig:After adding ''which brctl'' in the script it should have generated some output in xend.log. Please post xend.log Ian> x235:~ # ifconfig > eth0 Link encap:Ethernet HWaddr 00:09:6B:A5:B5:EE inet > addr:9.3.192.65 Bcast:9.3.192.255 Mask:255.255.255.0 UP > BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5356 > errors:0 dropped:0 overruns:0 frame:0 TX packets:374 errors:0 > dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 > RX bytes:732337 (715.1 Kb) TX bytes:48514 (47.3 Kb) > Interrupt:29 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX > packets:36 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 RX bytes:2880 (2.8 Kb) TX > bytes:2880 (2.8 Kb) > > Also I can not even do xm list: > > x235:~ # ps -ef|grep xend > root 22613 1 5 14:35 ? 00:00:00 python /usr/sbin/xend start > root 22614 22613 0 14:35 pts/0 00:00:00 python /usr/sbin/xend > start root 22615 22614 0 14:35 pts/0 00:00:00 python > /usr/sbin/xend start root 22616 22614 0 14:35 pts/0 00:00:00 > python /usr/sbin/xend start root 22617 22614 0 14:35 pts/0 > 00:00:00 python /usr/sbin/xend start root 22618 22614 0 14:35 > pts/0 00:00:00 python /usr/sbin/xend start root 23070 10759 0 > 14:35 pts/0 00:00:00 grep xend x235:~ # xm list (111, > ''Connection refused'') > Error: Error connecting to xend, is xend running? > > Switching back to the original network script, the network > works again. > > Not sure if I catched all the changes that you suggested. > Here is the diff between the new network file you sent and my > modified one: > > 123c123,124 > < brctl addbr ${bridge} > --- > > #brctl addbr ${bridge} > > create_bridge ${bridge} > 180c181,182 > < if ! ifdown ${netdev} ] ; then > --- > > which ifdown > > if ! ifdown ${netdev} ; then > 195,196c197,200 > < add_to_bridge ${bridge} vif0.0 > < add_to_bridge ${bridge} p${netdev} > --- > > #add_to_bridge ${bridge} vif0.0 > > #add_to_bridge ${bridge} p${netdev} > > brctl addif ${bridge} vif0.0 > > brctl addif ${bridge} p${netdev} > > Li > > > Inactive hide details for "Ian Pratt" > <m+Ian.Pratt@cl.cam.ac.uk>"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > > > > "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> > > 08/11/2005 05:17 PM > > > > To > > Li Ge/Austin/IBM@IBMUS > > > cc > > <ian.pratt@cl.cam.ac.uk>, "xen-devel" > <xen-devel@lists.xensource.com>, > <xen-devel-bounces@lists.xensource.com>, <ian.pratt@cl.cam.ac.uk> > > > Subject > > RE: [Xen-devel] new /etc/xen/network script > > > > Ok, I modifed the script. Here is the new result: > > > > After I started xend, the network connection of dom0 lost. > > OK, this is interesting. It''s the same symptoms as the old script. > > It looks like peth0 is receiving packets. Please confirm this with: > tcpdump -i peth0 > > What''s odd is that there''s no xen-br0 showing up in ifconfig. > I''d expect to see something like: > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:949 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:54097 (52.8 Kb) TX bytes:0 (0.0 b) > > Can you post the output of ''brctl show''. You should see: > > [root@commando-0 root]# brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.feffffffffff no vif0.0 > peth0 > > Also, please can you try replacing the following lines: > > - add_to_bridge ${bridge} vif0.0 > - add_to_bridge ${bridge} p${netdev} > + brctl addif ${bridge} vif0.0 > + brctl addif ${bridge} p${netdev} > > and earlier: > > + create_bridge ${bridge} > - brctl addbr ${bridge} > > > > Ian > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
ian, as the discussion in this thread, service os netwok will break after xend start. this simple patch can work on my mahine. but strange error still occur in xend.log and xend start takes more time with ifdown/ifup. @@ -192,6 +192,7 @@ ifconfig p${netdev} -arp down ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff ifconfig ${netdev} hw ether ${mac} + del_addrs p${netdev} add_to_bridge ${bridge} vif0.0 add_to_bridge ${bridge} p${netdev} ip link set vif0.0 up --------------xend.log------------------------ [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + set -e [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + OP=start [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + shift [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + for arg in ''"$@"'' [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + export bridge=xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + bridge=xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + for arg in ''"$@"'' [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + export antispoof=no [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + antispoof=no [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + bridge=xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + netdev=eth0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + antispoof=no [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + echo ''*network start bridge=xen-br0 netdev=eth0 antispoof=no'' [2005-08-16 23:14:19 xend] INFO (__init__:988) [network-bridge] network start bridge=xen-br0 netdev=eth0 antispoof=no [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + case ${OP} in [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + op_start [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + ''['' xen-br0 == null '']'' [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + create_bridge xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + local bridge=xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + brctl show [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + grep -q xen-br0 [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> xend.start 0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + brctl addbr xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + brctl stp xen-br0 off [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + brctl setfd xen-br0 0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + ifconfig xen-br0 up [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + ifconfig [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + grep -q veth0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + ifconfig veth0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + grep -q veth0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] ++ ifconfig eth0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] ++ grep HWadd [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] ++ sed -e ''s/.*\(..:..:..:..:..:..\).*/\1/'' [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + mac=00:0C:F1:FE:4C:5B [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + ifdown eth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + ip link set eth0 name peth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + ip link set veth0 name eth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + ifconfig peth0 -arp down [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + del_addrs peth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + local src=peth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + ip addr show dev peth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + egrep ''^ *inet '' Best Rgds Edwin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> ian, > as the discussion in this thread, service os netwok will > break after xend start. > this simple patch can work on my mahine. > but strange error still occur in xend.log and xend start > takes more time with ifdown/ifup.I guess the patch can''t do any harm, but why doesn''t ifdown remove the routes? Before starting xend, please can you post the output of the following sequence: ifconfig ifdown eth0 ifconfig Thanks, Ian> @@ -192,6 +192,7 @@ > ifconfig p${netdev} -arp down > ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff > ifconfig ${netdev} hw ether ${mac} > + del_addrs p${netdev} > add_to_bridge ${bridge} vif0.0 > add_to_bridge ${bridge} p${netdev} > ip link set vif0.0 up > > > --------------xend.log------------------------ > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + set -e > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + OP=start > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + shift > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + for arg in ''"$@"'' > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + export bridge=xen-br0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + bridge=xen-br0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + for arg in ''"$@"'' > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + export antispoof=no > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + antispoof=no > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + bridge=xen-br0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + netdev=eth0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + antispoof=no > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + echo ''*network start bridge=xen-br0 > netdev=eth0 antispoof=no'' > [2005-08-16 23:14:19 xend] INFO (__init__:988) > [network-bridge] network start bridge=xen-br0 netdev=eth0 antispoof=no > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + case ${OP} in > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + op_start > [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + ''['' > xen-br0 == null '']'' > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + create_bridge xen-br0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + local bridge=xen-br0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + brctl show > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + grep -q xen-br0 > [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> xend.start 0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + brctl addbr xen-br0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + brctl stp xen-br0 off > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + brctl setfd xen-br0 0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + ifconfig xen-br0 up > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + ifconfig > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + grep -q veth0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + ifconfig veth0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + grep -q veth0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] ++ ifconfig eth0 > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] ++ grep HWadd > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] ++ sed -e ''s/.*\(..:..:..:..:..:..\).*/\1/'' > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + mac=00:0C:F1:FE:4C:5B > [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] + ifdown eth0 > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ip link set eth0 name peth0 > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ip link set veth0 name eth0 > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ifconfig peth0 -arp down > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + del_addrs peth0 > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + local src=peth0 > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ip addr show dev peth0 > [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + egrep ''^ *inet '' > > Best Rgds > Edwin > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
***Before*** [root@vt-edwin ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B inet addr:172.16.219.31 Bcast:172.16.219.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:127 errors:0 dropped:0 overruns:0 frame:0 TX packets:65 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) ***After ifdown eth0 *** [root@vt-edwin ~]# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) but [root@vt-edwin ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B inet addr:172.16.219.31 Bcast:172.16.219.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:182 errors:0 dropped:0 overruns:0 frame:0 TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on 2005年8月16日 23:41:>> ian, >> as the discussion in this thread, service os netwok will >> break after xend start. >> this simple patch can work on my mahine. >> but strange error still occur in xend.log and xend start >> takes more time with ifdown/ifup. > > I guess the patch can''t do any harm, but why doesn''t ifdown remove the > routes? > > Before starting xend, please can you post the output of the following > sequence: > > ifconfig > ifdown eth0 > ifconfig > > Thanks, > Ian > > >> @@ -192,6 +192,7 @@ >> ifconfig p${netdev} -arp down >> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff >> ifconfig ${netdev} hw ether ${mac} >> + del_addrs p${netdev} >> add_to_bridge ${bridge} vif0.0 >> add_to_bridge ${bridge} p${netdev} >> ip link set vif0.0 up >> >> >> --------------xend.log------------------------ >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + set -e >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + OP=start >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + shift >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + for arg in ''"$@"'' >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + export bridge=xen-br0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + bridge=xen-br0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + for arg in ''"$@"'' >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + export antispoof=no >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + antispoof=no >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + bridge=xen-br0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + netdev=eth0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + antispoof=no >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + echo ''*network start bridge=xen-br0 >> netdev=eth0 antispoof=no'' >> [2005-08-16 23:14:19 xend] INFO (__init__:988) >> [network-bridge] network start bridge=xen-br0 netdev=eth0 >> antispoof=no [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + case ${OP} in >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + op_start >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >> ''['' xen-br0 == null '']'' [2005-08-16 23:14:19 xend] ERROR >> (__init__:988) [network-bridge] + create_bridge xen-br0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + local bridge=xen-br0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + brctl show >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + grep -q xen-br0 >> [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> xend.start 0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + brctl addbr xen-br0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + brctl stp xen-br0 off >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + brctl setfd xen-br0 0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + ifconfig xen-br0 up >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + ifconfig >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + grep -q veth0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + ifconfig veth0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + grep -q veth0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] ++ ifconfig eth0 >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] ++ grep HWadd >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] ++ sed -e ''s/.*\(..:..:..:..:..:..\).*/\1/'' >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + mac=00:0C:F1:FE:4C:5B >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) >> [network-bridge] + ifdown eth0 >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + ip link set eth0 name peth0 >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + ip link set veth0 name eth0 >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + ifconfig peth0 -arp down >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + del_addrs peth0 >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + local src=peth0 >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + ip addr show dev peth0 >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) >> [network-bridge] + egrep ''^ *inet '' >> >> Best Rgds >> Edwin_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
So, ifdown does succeed in taking the interface down. I wander why the routes aren't getting removed? Could you do: ifconfig netstat -rn ifdown eth0 netstat -rn ifconfig Thanks, Ian> -----Original Message----- > From: Zhai, Edwin [mailto:edwin.zhai@intel.com] > Sent: 16 August 2005 16:57 > To: Ian Pratt > Cc: xen-devel@lists.xensource.com; ian.pratt@cl.cam.ac.uk > Subject: RE: new /etc/xen/network script > > > ***Before*** > [root@vt-edwin ~]# ifconfig > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > > inet addr:172.16.219.31 Bcast:172.16.219.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:127 errors:0 dropped:0 overruns:0 > frame:0 > TX packets:65 errors:0 dropped:0 overruns:0 > carrier:0 > collisions:0 txqueuelen:1000 > > RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > ***After ifdown eth0 *** > [root@vt-edwin ~]# ifconfig > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > but > [root@vt-edwin ~]# ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > inet addr:172.16.219.31 Bcast:172.16.219.255 > Mask:255.255.255.0 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:182 errors:0 dropped:0 overruns:0 frame:0 > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on > 2005年8月16日 23:41: > > >> ian, > >> as the discussion in this thread, service os netwok will > break after > >> xend start. > >> this simple patch can work on my mahine. > >> but strange error still occur in xend.log and xend start > takes more > >> time with ifdown/ifup. > > > > I guess the patch can't do any harm, but why doesn't ifdown > remove the > > routes? > > > > Before starting xend, please can you post the output of the > following > > sequence: > > > > ifconfig > > ifdown eth0 > > ifconfig > > > > Thanks, > > Ian > > > > > >> @@ -192,6 +192,7 @@ > >> ifconfig p${netdev} -arp down > >> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff > >> ifconfig ${netdev} hw ether ${mac} > >> + del_addrs p${netdev} > >> add_to_bridge ${bridge} vif0.0 > >> add_to_bridge ${bridge} p${netdev} > >> ip link set vif0.0 up > >> > >> > >> --------------xend.log------------------------ > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> set -e > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> OP=start > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> shift > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> for arg in '"$@"' > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> export bridge=xen-br0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> bridge=xen-br0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> for arg in '"$@"' > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> export antispoof=no > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> antispoof=no > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> bridge=xen-br0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> netdev=eth0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> antispoof=no > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> echo '*network start bridge=xen-br0 netdev=eth0 antispoof=no' > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) [network-bridge] > >> network start bridge=xen-br0 netdev=eth0 antispoof=no [2005-08-16 > >> 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > case ${OP} in > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> op_start > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> '[' xen-br0 == null ']' [2005-08-16 23:14:19 xend] ERROR > >> (__init__:988) [network-bridge] + create_bridge xen-br0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> local bridge=xen-br0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> brctl show > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> grep -q xen-br0 > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> xend.start 0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> brctl addbr xen-br0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> brctl stp xen-br0 off > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> brctl setfd xen-br0 0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> ifconfig xen-br0 up > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> ifconfig > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> grep -q veth0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> ifconfig veth0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> grep -q veth0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] ++ > >> ifconfig eth0 > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] ++ > >> grep HWadd > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] ++ > >> sed -e 's/.*\(..:..:..:..:..:..\).*/\1/' > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> mac=00:0C:F1:FE:4C:5B > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > >> ifdown eth0 > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ip > >> link set eth0 name peth0 > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ip > >> link set veth0 name eth0 > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > >> ifconfig peth0 -arp down > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > >> ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > >> ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > >> del_addrs peth0 > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > >> local src=peth0 > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] + ip > >> addr show dev peth0 > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > >> egrep '^ *inet ' > >> > >> Best Rgds > >> Edwin >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I, too, am having network related issues. I am now seeing this problem on a FC3 box, which previously had worked just fine. The networking is working fine before I enter ''xend start''. No changes are made to the network-bridge script that comes with the source, and the machine has only only nic, eth0. ifconfig before ''xend start'': [root@dbarrera ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0D:60:F0:C5:C8 inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:88 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12299 (12.0 KiB) TX bytes:11426 (11.1 KiB) Base address:0x2000 Memory:e8100000-e8120000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) [root@dbarrera ~]# brctl show bridge name bridge id STP enabled interfaces [root@dbarrera ~]# when ''xend start'' is entered, these messages appear on console: store_evtchn = 16 XENBUS xs_read_watch: 0 ifconfig AFTER ''xend start''eth0 Link encap:Ethernet HWaddr 00:0D:60:F0:C5:C8 inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:380 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:28046 (27.3 KiB) TX bytes:426 (426.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:501 errors:0 dropped:0 overruns:0 frame:0 TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44601 (43.5 KiB) TX bytes:12036 (11.7 KiB) Base address:0x2000 Memory:e8100000-e8120000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:380 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:426 (426.0 b) TX bytes:28046 (27.3 KiB) xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:375 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:22208 (21.6 KiB) TX bytes:0 (0.0 b) [root@dbarrera ~]# brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.feffffffffff no peth0 vif0.0 xen-br0 is up, but networking is dead. This is different from the previous issues where xen-br0 was not coming up, but when started manually networking resumed. On 2 other machines, networking is up and working, Dom0 has networking running correctly, but when I start a domU, it does not have networking. I have 3 similar machines, only one of which has a domU with working network; the other two don''t, even though they have very similar setups. This *may* end up being a setup issue (although these same setups worked before), but I can''t figure out what that could be--everything looks like it is supposed to be.> So, ifdown does succeed in taking the interface down. I wander why the routes aren''t getting removed? > > Could you do: > ifconfig > netstat -rn > ifdown eth0 > netstat -rn > ifconfig > > Thanks, > Ian > > > > -----Original Message----- > > From: Zhai, Edwin [mailto:edwin.zhai@intel.com] > > Sent: 16 August 2005 16:57 > > To: Ian Pratt > > Cc: xen-devel@lists.xensource.com; ian.pratt@cl.cam.ac.uk > > Subject: RE: new /etc/xen/network script > > > > > > ***Before*** > > [root@vt-edwin ~]# ifconfig > > > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > > > > inet addr:172.16.219.31 Bcast:172.16.219.255 > > Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > RX packets:127 errors:0 dropped:0 overruns:0 > > frame:0 > > TX packets:65 errors:0 dropped:0 overruns:0 > > carrier:0 > > collisions:0 txqueuelen:1000 > > > > RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB) > > > > > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > ***After ifdown eth0 *** > > [root@vt-edwin ~]# ifconfig > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > > > but > > [root@vt-edwin ~]# ifconfig -a > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > > inet addr:172.16.219.31 Bcast:172.16.219.255 > > Mask:255.255.255.0 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:182 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > > > Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on > > 2005年8月16日 23:41: > > > > >> ian, > > >> as the discussion in this thread, service os netwok will > > break after > > >> xend start. > > >> this simple patch can work on my mahine. > > >> but strange error still occur in xend.log and xend start > > takes more > > >> time with ifdown/ifup. > > > > > > I guess the patch can''t do any harm, but why doesn''t ifdown > > remove the > > > routes? > > > > > > Before starting xend, please can you post the output of the > > following > > > sequence: > > > > > > ifconfig > > > ifdown eth0 > > > ifconfig > > > > > > Thanks, > > > Ian > > > > > > > > >> @@ -192,6 +192,7 @@ > > >> ifconfig p${netdev} -arp down > > >> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff > > >> ifconfig ${netdev} hw ether ${mac} > > >> + del_addrs p${netdev} > > >> add_to_bridge ${bridge} vif0.0 > > >> add_to_bridge ${bridge} p${netdev} > > >> ip link set vif0.0 up > > >> > > >> > > >> --------------xend.log------------------------ > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> set -e > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> OP=start > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> shift > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> for arg in ''"$@"'' > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> export bridge=xen-br0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> bridge=xen-br0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> for arg in ''"$@"'' > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> export antispoof=no > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> antispoof=no > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> bridge=xen-br0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> netdev=eth0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> antispoof=no > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> echo ''*network start bridge=xen-br0 netdev=eth0 antispoof=no'' > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) [network-bridge] > > >> network start bridge=xen-br0 netdev=eth0 antispoof=no [2005-08-16 > > >> 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > case ${OP} in > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> op_start > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> ''['' xen-br0 == null '']'' [2005-08-16 23:14:19 xend] ERROR > > >> (__init__:988) [network-bridge] + create_bridge xen-br0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> local bridge=xen-br0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> brctl show > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> grep -q xen-br0 > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> xend.start 0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> brctl addbr xen-br0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> brctl stp xen-br0 off > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> brctl setfd xen-br0 0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> ifconfig xen-br0 up > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> ifconfig > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> grep -q veth0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> ifconfig veth0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> grep -q veth0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] ++ > > >> ifconfig eth0 > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] ++ > > >> grep HWadd > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] ++ > > >> sed -e ''s/.*\(..:..:..:..:..:..\).*/\1/'' > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> mac=00:0C:F1:FE:4C:5B > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > >> ifdown eth0 > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] + ip > > >> link set eth0 name peth0 > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] + ip > > >> link set veth0 name eth0 > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > > >> ifconfig peth0 -arp down > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > > >> ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > > >> ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > > >> del_addrs peth0 > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > > >> local src=peth0 > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] + ip > > >> addr show dev peth0 > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + > > >> egrep ''^ *inet '' > > >> > > >> Best Rgds > > >> Edwin > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> I, too, am having network related issues. I am now seeing > this problem on a FC3 box, which previously had worked just > fine. The networking is working fine before I enter 'xend > start'. No changes are made to the network-bridge script that > comes with the source, and the machine has only only nic, eth0.Grrr. Please can you do a 'netstat -rn' before and after. What kind of network card is this? The TX/RX counters for the new eth0 are non zero. Are they going up? In what whay does networking not work? Can you use tcpdump on eth0 to determine whether packets from the outside world are arriving. If not, what about peth0? (Bare in mind that if you only have one-way connectivity the only packets you're see are arps, not icmp pings or anything else) Ian> ifconfig before 'xend start': > > [root@dbarrera ~]# ifconfig > eth0 Link encap:Ethernet HWaddr 00:0D:60:F0:C5:C8 > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > TX packets:88 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:12299 (12.0 KiB) TX bytes:11426 (11.1 KiB) > Base address:0x2000 Memory:e8100000-e8120000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) > > [root@dbarrera ~]# brctl show > bridge name bridge id STP enabled interfaces > [root@dbarrera ~]# > > when 'xend start' is entered, these messages appear on console: > store_evtchn = 16 > XENBUS xs_read_watch: 0 > > ifconfig AFTER 'xend start'eth0 Link encap:Ethernet > HWaddr 00:0D:60:F0:C5:C8 > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:380 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:28046 (27.3 KiB) TX bytes:426 (426.0 b) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:501 errors:0 dropped:0 overruns:0 frame:0 > TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:44601 (43.5 KiB) TX bytes:12036 (11.7 KiB) > Base address:0x2000 Memory:e8100000-e8120000 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:380 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:426 (426.0 b) TX bytes:28046 (27.3 KiB) > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:375 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:22208 (21.6 KiB) TX bytes:0 (0.0 b) > > [root@dbarrera ~]# brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.feffffffffff no peth0 > vif0.0 > > xen-br0 is up, but networking is dead. This is different from > the previous issues where xen-br0 was not coming up, but when > started manually networking resumed. > > On 2 other machines, networking is up and working, Dom0 has > networking running correctly, but when I start a domU, it > does not have networking. I have 3 similar machines, only one > of which has a domU with working network; the other two > don't, even though they have very similar setups. This *may* > end up being a setup issue (although these same setups worked > before), but I can't figure out what that could > be--everything looks like it is supposed to be. > > > So, ifdown does succeed in taking the interface down. I > wander why the routes aren't getting removed? > > > > Could you do: > > ifconfig > > netstat -rn > > ifdown eth0 > > netstat -rn > > ifconfig > > > > Thanks, > > Ian > > > > > > > -----Original Message----- > > > From: Zhai, Edwin [mailto:edwin.zhai@intel.com] > > > Sent: 16 August 2005 16:57 > > > To: Ian Pratt > > > Cc: xen-devel@lists.xensource.com; ian.pratt@cl.cam.ac.uk > > > Subject: RE: new /etc/xen/network script > > > > > > > > > ***Before*** > > > [root@vt-edwin ~]# ifconfig > > > > > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > > > > > > inet addr:172.16.219.31 Bcast:172.16.219.255 > > > Mask:255.255.255.0 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > > > RX packets:127 errors:0 dropped:0 overruns:0 > > > frame:0 > > > TX packets:65 errors:0 dropped:0 overruns:0 > > > carrier:0 > > > collisions:0 txqueuelen:1000 > > > > > > RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB) > > > > > > > > > > > > lo Link encap:Local Loopback > > > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > > > ***After ifdown eth0 *** > > > [root@vt-edwin ~]# ifconfig > > > > > > lo Link encap:Local Loopback > > > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > > > > > > but > > > [root@vt-edwin ~]# ifconfig -a > > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > > > inet addr:172.16.219.31 Bcast:172.16.219.255 > > > Mask:255.255.255.0 > > > BROADCAST MULTICAST MTU:1500 Metric:1 > > > RX packets:182 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB) > > > > > > lo Link encap:Local Loopback > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > > BROADCAST MULTICAST MTU:1500 Metric:1 > > > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > > BROADCAST MULTICAST MTU:1500 Metric:1 > > > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on > > > 2005年8月16日 23:41: > > > > > > >> ian, > > > >> as the discussion in this thread, service os netwok will > > > break after > > > >> xend start. > > > >> this simple patch can work on my mahine. > > > >> but strange error still occur in xend.log and xend start > > > takes more > > > >> time with ifdown/ifup. > > > > > > > > I guess the patch can't do any harm, but why doesn't ifdown > > > remove the > > > > routes? > > > > > > > > Before starting xend, please can you post the output of the > > > following > > > > sequence: > > > > > > > > ifconfig > > > > ifdown eth0 > > > > ifconfig > > > > > > > > Thanks, > > > > Ian > > > > > > > > > > > >> @@ -192,6 +192,7 @@ > > > >> ifconfig p${netdev} -arp down > > > >> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff > > > >> ifconfig ${netdev} hw ether ${mac} > > > >> + del_addrs p${netdev} > > > >> add_to_bridge ${bridge} vif0.0 > > > >> add_to_bridge ${bridge} p${netdev} > > > >> ip link set vif0.0 up > > > >> > > > >> > > > >> --------------xend.log------------------------ > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + set -e > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + OP=start > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + shift > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + for arg in '"$@"' > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + export bridge=xen-br0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + bridge=xen-br0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + for arg in '"$@"' > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + export antispoof=no > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + antispoof=no > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + bridge=xen-br0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + netdev=eth0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + antispoof=no > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + echo '*network start bridge=xen-br0 netdev=eth0 antispoof=no' > > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) > [network-bridge] > > > >> network start bridge=xen-br0 netdev=eth0 antispoof=no > [2005-08-16 > > > >> 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > > case ${OP} in > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + op_start > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + '[' xen-br0 == null ']' [2005-08-16 23:14:19 xend] ERROR > > > >> (__init__:988) [network-bridge] + create_bridge xen-br0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + local bridge=xen-br0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + brctl show > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + grep -q xen-br0 > > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> > xend.start > > > >> 0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + brctl addbr xen-br0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + brctl stp xen-br0 off > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + brctl setfd xen-br0 0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + ifconfig xen-br0 up > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + ifconfig > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + grep -q veth0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + ifconfig veth0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + grep -q veth0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > > [network-bridge] ++ > > > >> ifconfig eth0 > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > > [network-bridge] ++ > > > >> grep HWadd > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > > [network-bridge] ++ > > > >> sed -e 's/.*\(..:..:..:..:..:..\).*/\1/' > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + mac=00:0C:F1:FE:4C:5B > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > [network-bridge] > > > >> + ifdown eth0 > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > > [network-bridge] + ip > > > >> link set eth0 name peth0 > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > > [network-bridge] + ip > > > >> link set veth0 name eth0 > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] > > > >> + ifconfig peth0 -arp down > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] > > > >> + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] > > > >> + ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] > > > >> + del_addrs peth0 > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] > > > >> + local src=peth0 > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > > [network-bridge] + ip > > > >> addr show dev peth0 > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > [network-bridge] > > > >> + egrep '^ *inet ' > > > >> > > > >> Best Rgds > > > >> Edwin > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > -- > Regards, > > David F Barrera > Linux Technology Center > Systems and Technology Group, IBM > > "The wisest men follow their own direction. " > Euripides > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 2005-08-16 at 17:51 +0100, Ian Pratt wrote:> > I, too, am having network related issues. I am now seeing > > this problem on a FC3 box, which previously had worked just > > fine. The networking is working fine before I enter ''xend > > start''. No changes are made to the network-bridge script that > > comes with the source, and the machine has only only nic, eth0. > > Grrr. Please can you do a ''netstat -rn'' before and after.I should point out that the new network-bridge script appears to have cured the original problem on the SLES 9 boxes; at least xen-br0 is coming up and Dom0 retains networking on those boxes. On the FC3 box: before:[root@dbarrera ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 9.53.94.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 0.0.0.0 9.53.94.1 0.0.0.0 UG 0 0 0 eth0> What kind of network card is this?Intel 82541EI Gigabit Ethernet Controller (Copper)> > The TX/RX counters for the new eth0 are non zero. Are they going up? > In what whay does networking not work?I cannot connect to or from the outside (ssh, ping, nfs mounts, etc).> Can you use tcpdump on eth0 to determine whether packets from the outside world are arriving.It seems that packets from the outside world are coming in. I entered ''tcpdump -n -i eth0 host 9.53.94.235'' then when I tried to ssh from the other machine, it shows up on the tcpdump. But the ssh session is never established. Ping shows up as well.> If not, what about peth0?Same.> (Bare in mind that if you only have one-way connectivity the only packets you''re see are arps, not icmp pings or anything else) > > Ian > > > ifconfig before ''xend start'': > > > > [root@dbarrera ~]# ifconfig > > eth0 Link encap:Ethernet HWaddr 00:0D:60:F0:C5:C8 > > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:88 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:12299 (12.0 KiB) TX bytes:11426 (11.1 KiB) > > Base address:0x2000 Memory:e8100000-e8120000 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) > > > > [root@dbarrera ~]# brctl show > > bridge name bridge id STP enabled interfaces > > [root@dbarrera ~]# > > > > when ''xend start'' is entered, these messages appear on console: > > store_evtchn = 16 > > XENBUS xs_read_watch: 0 > > > > ifconfig AFTER ''xend start''eth0 Link encap:Ethernet > > HWaddr 00:0D:60:F0:C5:C8 > > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:380 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:28046 (27.3 KiB) TX bytes:426 (426.0 b) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) > > > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > inet addr:9.53.94.235 Bcast:9.53.94.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > > RX packets:501 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:44601 (43.5 KiB) TX bytes:12036 (11.7 KiB) > > Base address:0x2000 Memory:e8100000-e8120000 > > > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:3 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:380 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:426 (426.0 b) TX bytes:28046 (27.3 KiB) > > > > xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:375 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:22208 (21.6 KiB) TX bytes:0 (0.0 b) > > > > [root@dbarrera ~]# brctl show > > bridge name bridge id STP enabled interfaces > > xen-br0 8000.feffffffffff no peth0 > > vif0.0 > > > > xen-br0 is up, but networking is dead. This is different from > > the previous issues where xen-br0 was not coming up, but when > > started manually networking resumed. > > > > On 2 other machines, networking is up and working, Dom0 has > > networking running correctly, but when I start a domU, it > > does not have networking. I have 3 similar machines, only one > > of which has a domU with working network; the other two > > don''t, even though they have very similar setups. This *may* > > end up being a setup issue (although these same setups worked > > before), but I can''t figure out what that could > > be--everything looks like it is supposed to be. > > > > > So, ifdown does succeed in taking the interface down. I > > wander why the routes aren''t getting removed? > > > > > > Could you do: > > > ifconfig > > > netstat -rn > > > ifdown eth0 > > > netstat -rn > > > ifconfig > > > > > > Thanks, > > > Ian > > > > > > > > > > -----Original Message----- > > > > From: Zhai, Edwin [mailto:edwin.zhai@intel.com] > > > > Sent: 16 August 2005 16:57 > > > > To: Ian Pratt > > > > Cc: xen-devel@lists.xensource.com; ian.pratt@cl.cam.ac.uk > > > > Subject: RE: new /etc/xen/network script > > > > > > > > > > > > ***Before*** > > > > [root@vt-edwin ~]# ifconfig > > > > > > > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > > > > > > > > inet addr:172.16.219.31 Bcast:172.16.219.255 > > > > Mask:255.255.255.0 > > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > > > > > RX packets:127 errors:0 dropped:0 overruns:0 > > > > frame:0 > > > > TX packets:65 errors:0 dropped:0 overruns:0 > > > > carrier:0 > > > > collisions:0 txqueuelen:1000 > > > > > > > > RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB) > > > > > > > > > > > > > > > > lo Link encap:Local Loopback > > > > > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > > > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > > > > > ***After ifdown eth0 *** > > > > [root@vt-edwin ~]# ifconfig > > > > > > > > lo Link encap:Local Loopback > > > > > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > > > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > > > > > > > > > but > > > > [root@vt-edwin ~]# ifconfig -a > > > > eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B > > > > inet addr:172.16.219.31 Bcast:172.16.219.255 > > > > Mask:255.255.255.0 > > > > BROADCAST MULTICAST MTU:1500 Metric:1 > > > > RX packets:182 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:1000 > > > > RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB) > > > > > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) > > > > > > > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > > > BROADCAST MULTICAST MTU:1500 Metric:1 > > > > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > > > BROADCAST MULTICAST MTU:1500 Metric:1 > > > > RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > > > Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on > > > > 2005年8月16日 23:41: > > > > > > > > >> ian, > > > > >> as the discussion in this thread, service os netwok will > > > > break after > > > > >> xend start. > > > > >> this simple patch can work on my mahine. > > > > >> but strange error still occur in xend.log and xend start > > > > takes more > > > > >> time with ifdown/ifup. > > > > > > > > > > I guess the patch can''t do any harm, but why doesn''t ifdown > > > > remove the > > > > > routes? > > > > > > > > > > Before starting xend, please can you post the output of the > > > > following > > > > > sequence: > > > > > > > > > > ifconfig > > > > > ifdown eth0 > > > > > ifconfig > > > > > > > > > > Thanks, > > > > > Ian > > > > > > > > > > > > > > >> @@ -192,6 +192,7 @@ > > > > >> ifconfig p${netdev} -arp down > > > > >> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff > > > > >> ifconfig ${netdev} hw ether ${mac} > > > > >> + del_addrs p${netdev} > > > > >> add_to_bridge ${bridge} vif0.0 > > > > >> add_to_bridge ${bridge} p${netdev} > > > > >> ip link set vif0.0 up > > > > >> > > > > >> > > > > >> --------------xend.log------------------------ > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + set -e > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + OP=start > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + shift > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + for arg in ''"$@"'' > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + export bridge=xen-br0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + bridge=xen-br0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + for arg in ''"$@"'' > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + export antispoof=no > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + antispoof=no > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + bridge=xen-br0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + netdev=eth0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + antispoof=no > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + echo ''*network start bridge=xen-br0 netdev=eth0 antispoof=no'' > > > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) > > [network-bridge] > > > > >> network start bridge=xen-br0 netdev=eth0 antispoof=no > > [2005-08-16 > > > > >> 23:14:19 xend] ERROR (__init__:988) [network-bridge] + > > > > case ${OP} in > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + op_start > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ''['' xen-br0 == null '']'' [2005-08-16 23:14:19 xend] ERROR > > > > >> (__init__:988) [network-bridge] + create_bridge xen-br0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + local bridge=xen-br0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + brctl show > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + grep -q xen-br0 > > > > >> [2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> > > xend.start > > > > >> 0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + brctl addbr xen-br0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + brctl stp xen-br0 off > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + brctl setfd xen-br0 0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ifconfig xen-br0 up > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ifconfig > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + grep -q veth0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ifconfig veth0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + grep -q veth0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > > > [network-bridge] ++ > > > > >> ifconfig eth0 > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > > > [network-bridge] ++ > > > > >> grep HWadd > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > > > [network-bridge] ++ > > > > >> sed -e ''s/.*\(..:..:..:..:..:..\).*/\1/'' > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + mac=00:0C:F1:FE:4C:5B > > > > >> [2005-08-16 23:14:19 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ifdown eth0 > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > > > [network-bridge] + ip > > > > >> link set eth0 name peth0 > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > > > [network-bridge] + ip > > > > >> link set veth0 name eth0 > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ifconfig peth0 -arp down > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + del_addrs peth0 > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + local src=peth0 > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > > > [network-bridge] + ip > > > > >> addr show dev peth0 > > > > >> [2005-08-16 23:14:20 xend] ERROR (__init__:988) > > [network-bridge] > > > > >> + egrep ''^ *inet '' > > > > >> > > > > >> Best Rgds > > > > >> Edwin > > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > -- > > Regards, > > > > David F Barrera > > Linux Technology Center > > Systems and Technology Group, IBM > > > > "The wisest men follow their own direction. " > > Euripides > > > >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:> So, ifdown does succeed in taking the interface down. I wander why the routes aren''t getting removed?Are we sure that''s the case? I think what is happening is that the routes are going down, but to bring up peth0 again, we only do a ip link set peth0 up, which creates an interface route, but does not automatically generate a default route (since we aren''t transferring routes in this case). The netstat -rn should confirm that.> Could you do: > ifconfig > netstat -rn > ifdown eth0 > netstat -rn > ifconfig > > Thanks, > IanI am scratching my head on how the del_addr should make a difference here, since the ifdown should have taken down the routes.. There are several ways to clean up, if the above is correct. thanks, Nivedita> > >>-----Original Message----- >>From: Zhai, Edwin [mailto:edwin.zhai@intel.com] >>Sent: 16 August 2005 16:57 >>To: Ian Pratt >>Cc: xen-devel@lists.xensource.com; ian.pratt@cl.cam.ac.uk >>Subject: RE: new /etc/xen/network script >> >> >>***Before*** >>[root@vt-edwin ~]# ifconfig >> >>eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B >> >> inet addr:172.16.219.31 Bcast:172.16.219.255 >>Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> >> RX packets:127 errors:0 dropped:0 overruns:0 >>frame:0 >> TX packets:65 errors:0 dropped:0 overruns:0 >>carrier:0 >> collisions:0 txqueuelen:1000 >> >> RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB) >> >> >> >>lo Link encap:Local Loopback >> >> inet addr:127.0.0.1 Mask:255.0.0.0 >> >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> >> RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) >> >>***After ifdown eth0 *** >>[root@vt-edwin ~]# ifconfig >> >>lo Link encap:Local Loopback >> >> inet addr:127.0.0.1 Mask:255.0.0.0 >> >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> >> RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) >> >> >>but >>[root@vt-edwin ~]# ifconfig -a >>eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B >> inet addr:172.16.219.31 Bcast:172.16.219.255 >>Mask:255.255.255.0 >> BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:182 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB) >> >>lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) >> >>veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 >> BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) >> >>vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) >> >>Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on >>2005年8月16日 23:41: >> >> >>>>ian, >>>>as the discussion in this thread, service os netwok will >> >>break after >> >>>>xend start. >>>>this simple patch can work on my mahine. >>>>but strange error still occur in xend.log and xend start >> >>takes more >> >>>>time with ifdown/ifup. >>> >>>I guess the patch can''t do any harm, but why doesn''t ifdown >> >>remove the >> >>>routes? >>> >>>Before starting xend, please can you post the output of the >> >>following >> >>>sequence: >>> >>> ifconfig >>> ifdown eth0 >>> ifconfig >>> >>>Thanks, >>>Ian >>> >>> >>> >>>>@@ -192,6 +192,7 @@ >>>> ifconfig p${netdev} -arp down >>>> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff >>>> ifconfig ${netdev} hw ether ${mac} >>>>+ del_addrs p${netdev} >>>> add_to_bridge ${bridge} vif0.0 >>>> add_to_bridge ${bridge} p${netdev} >>>> ip link set vif0.0 up >>>> >>>> >>>>--------------xend.log------------------------ >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>set -e >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>OP=start >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>shift >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>for arg in ''"$@"'' >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>export bridge=xen-br0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>bridge=xen-br0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>for arg in ''"$@"'' >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>export antispoof=no >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>antispoof=no >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>bridge=xen-br0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>netdev=eth0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>antispoof=no >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>echo ''*network start bridge=xen-br0 netdev=eth0 antispoof=no'' >>>>[2005-08-16 23:14:19 xend] INFO (__init__:988) [network-bridge] >>>>network start bridge=xen-br0 netdev=eth0 antispoof=no [2005-08-16 >>>>23:14:19 xend] ERROR (__init__:988) [network-bridge] + >> >>case ${OP} in >> >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>op_start >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>''['' xen-br0 == null '']'' [2005-08-16 23:14:19 xend] ERROR >>>>(__init__:988) [network-bridge] + create_bridge xen-br0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>local bridge=xen-br0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>brctl show >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>grep -q xen-br0 >>>>[2005-08-16 23:14:19 xend] INFO (__init__:988) EVENT> xend.start 0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>brctl addbr xen-br0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>brctl stp xen-br0 off >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>brctl setfd xen-br0 0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>ifconfig xen-br0 up >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>ifconfig >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>grep -q veth0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>ifconfig veth0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>grep -q veth0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) >> >>[network-bridge] ++ >> >>>>ifconfig eth0 >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) >> >>[network-bridge] ++ >> >>>>grep HWadd >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) >> >>[network-bridge] ++ >> >>>>sed -e ''s/.*\(..:..:..:..:..:..\).*/\1/'' >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>mac=00:0C:F1:FE:4C:5B >>>>[2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] + >>>>ifdown eth0 >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) >> >>[network-bridge] + ip >> >>>>link set eth0 name peth0 >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) >> >>[network-bridge] + ip >> >>>>link set veth0 name eth0 >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + >>>>ifconfig peth0 -arp down >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + >>>>ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + >>>>ifconfig eth0 hw ether 00:0C:F1:FE:4C:5B >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + >>>>del_addrs peth0 >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + >>>>local src=peth0 >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) >> >>[network-bridge] + ip >> >>>>addr show dev peth0 >>>>[2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] + >>>>egrep ''^ *inet '' >>>> >>>>Best Rgds >>>>Edwin >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>Xen-devel mailing list >>Xen-devel@lists.xensource.com >>http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nivedita Singhvi wrote:> Ian Pratt wrote: > >> So, ifdown does succeed in taking the interface down. I wander why the >> routes aren''t getting removed? > > > Are we sure that''s the case? I think what is happening is > that the routes are going down, but to bring up peth0 > again, we only do a ip link set peth0 up, which creates > an interface route, but does not automatically generate > a default route (since we aren''t transferring routes > in this case).Urgh. Just synced with the correct script. One potential issue is the link set of peth0, which creates an interface route for peth0, at least on my currently broken box. The ifup of eth0 (veth0) will try to add a duplicate route for the primary subnet via eth0. Can''t validate or test any of the above since my box is crashing at boot, unrelated issue, will dig into this tmrw further when I get onto a box.. This in no way explains why having the del_addrs works for him when it''s prior to the link set up of peth0 (??), so this isn''t the fatal error. Would this make more sense: to have the route removal happen as so: --- network-bridge.orig 2005-08-17 03:38:13.000000000 -0700 +++ network-bridge 2005-08-17 04:08:33.298424365 -0700 @@ -197,6 +197,7 @@ ip link set ${bridge} up ip link set vif0.0 up ip link set p${netdev} up + del_addrs p${netdev} if ! ifup ${netdev} ; then if [ ${kip} ] ; then # use the addresses we grocked from proc/cmdline Just for testing.. signed-off-by Nivedita Singhvi niv#us.ibm.com thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> One potential issue is the link set of peth0, which creates > an interface route for peth0, at least on my currently broken > box. The ifup of eth0 (veth0) will try to add a duplicate > route for the primary subnet via eth0. Can''t validate or test > any of the above since my box is crashing at boot, unrelated > issue, will dig into this tmrw further when I get onto a box.. > > This in no way explains why having the del_addrs works for > him when it''s prior to the link set up of peth0 (??), so this > isn''t the fatal error.No, I messed up the inclusion of Edwin''s patch as I failed to understand the root cause. What I don''t understand is why the link set up on peth0 causes an address to appear. I thought it might be an old address from when it was eth0 getting resurected, hence the line I added. I wander if ''ifconfig ${netdev} 0.0.0.0 down'' would work better? Ian> Would this make more sense: to have the route removal happen as so: > > --- network-bridge.orig 2005-08-17 03:38:13.000000000 -0700 > +++ network-bridge 2005-08-17 04:08:33.298424365 -0700 > @@ -197,6 +197,7 @@ > ip link set ${bridge} up > ip link set vif0.0 up > ip link set p${netdev} up > + del_addrs p${netdev} > if ! ifup ${netdev} ; then > if [ ${kip} ] ; then > # use the addresses we grocked from > proc/cmdline > > Just for testing.. > > signed-off-by Nivedita Singhvi niv#us.ibm.com > > thanks, > Nivedita > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nivedita Singhvi wrote:> This in no way explains why having the del_addrs works > for him when it''s prior to the link set up of peth0 (??), > so this isn''t the fatal error.Guh. ifdown doesn''t delete the addrs, and once they are, via del_addrs, the link up doesn''t result in route creation. thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:> I thought it might be an old address from when it was eth0 getting > resurected, hence the line I added. I wander if ''ifconfig ${netdev} > 0.0.0.0 down'' would work better?One of the advantages to using the ifup/ifdown distro interface manipulation scripts is to also have them take care of the other things (radvd restart, ipv6, ipsec issues, ifup/down*local* scripts which might be doing other things when interfaces go up and down). We aren''t taking care of a lot of the other subsystems here, and I see the advantage in using the system configuration scripts as far as possible. The ifconfig line above would work in most cases, though, works for me ;). thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Nivedita Singhvi wrote: > > > This in no way explains why having the del_addrs works for him when > > it''s prior to the link set up of peth0 (??), so this isn''t > the fatal > > error. > > Guh. ifdown doesn''t delete the addrs, and once they are, via > del_addrs, the link up doesn''t result in route creation.What distro is this on? You''re not also setting the address via an ip= line on the kernel command line, or via an initrd? What''s the contents of your ifcfg-eth0 file? (you may have multiple under different profiles) Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:>>Guh. ifdown doesn''t delete the addrs, and once they are, via >>del_addrs, the link up doesn''t result in route creation. > > > What distro is this on? > > You''re not also setting the address via an ip= line on the kernel > command line, or via an initrd? > > What''s the contents of your ifcfg-eth0 file? (you may have multiple > under different profiles) > > Ian(Sorry for the verbosity here) FC3. Not setting address via kernel cmd line. ROOT:hex:/tmp]> ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0D:60:C9:52:89 inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20d:60ff:fec9:5289/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1594 errors:0 dropped:0 overruns:0 frame:0 TX packets:222 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:495161 (483.5 KiB) TX bytes:22079 (21.5 KiB) Base address:0x8000 Memory:c0220000-c0240000 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:1871 errors:0 dropped:0 overruns:0 frame:0 TX packets:1871 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2127980 (2.0 MiB) TX bytes:2127980 (2.0 MiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) ROOT:hex:/tmp]> netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.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 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 ROOT:hex:/tmp]> ifdown eth0 + . /etc/init.d/functions ++ TEXTDOMAIN=initscripts ++ umask 022 ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin ++ export PATH ++ ''['' -z '''' '']'' ++ COLUMNS=80 ++ ''['' -z '''' '']'' +++ /sbin/consoletype ++ CONSOLETYPE=pty ++ ''['' -f /etc/sysconfig/i18n -a -z '''' '']'' ++ . /etc/sysconfig/i18n +++ LANG=en_US.UTF-8 +++ SUPPORTED=en_US.UTF-8:en_US:en +++ SYSFONT=latarcyrheb-sun16 ++ ''['' pty ''!='' pty '']'' :0++ ''['' -n '''' '']'' ++ export LANG ++ ''['' -z '''' '']'' ++ ''['' -f /etc/sysconfig/init '']'' ++ . /etc/sysconfig/init +++ BOOTUP=color +++ GRAPHICAL=yes +++ RES_COL=60 +++ MOVE_TO_COL=''echo -en \033[60G'' +++ SETCOLOR_SUCCESS=''echo -en \033[0;32m'' +++ SETCOLOR_FAILURE=''echo -en \033[0;31m'' +++ SETCOLOR_WARNING=''echo -en \033[0;33m'' +++ SETCOLOR_NORMAL=''echo -en \033[0;39m'' +++ LOGLEVEL=3 +++ PROMPT=yes ++ ''['' pty = serial '']'' ++ ''['' color ''!='' verbose '']'' ++ INITLOG_ARGS=-q + cd /etc/sysconfig/network-scripts + . network-functions ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin ++ export PATH + ''['' -f ../network '']'' + . ../network ++ NETWORKING=yes ++ HOSTNAME=hex + CONFIG=eth0 + ''['' -z eth0 '']'' + need_config eth0 + CONFIG=ifcfg-eth0 + ''['' -f ifcfg-eth0 '']'' + return + ''['' -f ifcfg-eth0 '']'' + ''['' 0 ''!='' 0 '']'' + source_config ++ basename ifcfg-eth0 ++ sed ''s/^ifcfg-//g'' + DEVNAME=eth0 + basename ifcfg-eth0 + grep -q ''[^g]-'' + . ifcfg-eth0 ++ DEVICE=eth0 ++ BOOTPROTO=dhcp ++ ONBOOT=yes ++ TYPE=Ethernet + ''['' -r keys-eth0 '']'' + case "$TYPE" in + DEVICETYPE=eth + ''['' -z eth '']'' + ''['' -z '''' -a -n '''' '']'' + ''['' -z '''' '']'' + REALDEVICE=eth0 + ''['' eth0 ''!='' eth0 '']'' + ISALIAS=no + ''['' -n '''' '']'' + ''['' -n '''' '']'' + ''['' -x /sbin/ifdown-pre-local '']'' + OTHERSCRIPT=/etc/sysconfig/network-scripts/ifdown-eth + ''['' -x /etc/sysconfig/network-scripts/ifdown-eth '']'' + ''['' -n '''' -a -x /usr/sbin/brctl '']'' + . /etc/sysconfig/network ++ NETWORKING=yes ++ HOSTNAME=hex + check_device_down eth0 + echo eth0 + grep -q : + LC_ALL=C + ip -o link ls dev eth0 + grep -q ,UP + return 1 + ''['' -n '''' -a -z '''' '']'' + ''['' '''' = yes '']'' + retcode=0 + ''['' dhcp = bootp -o dhcp = dhcp '']'' ++ pidof -x dhclient + ''['' -n 2344 '']'' + ''['' -f /var/run/dhclient-eth0.pid '']'' ++ cat /var/run/dhclient-eth0.pid + kill 2344 + retcode=0 ++ pidof -x dhcpcd + ''['' -n '''' '']'' ++ pidof -x pump + ''['' -n '''' '']'' + ''['' eth0 = eth0 '']'' + ip link set dev eth0 down + ''['' 0 = 0 '']'' + retcode=0 + waited=0 + check_device_down eth0 + echo eth0 + grep -q : + LC_ALL=C + ip -o link ls dev eth0 + grep -q ,UP + return 0 + ''['' -n '''' -a -x /sbin/iwconfig '']'' + ''['' 0 = 0 '']'' + /etc/sysconfig/network-scripts/ifdown-post ifcfg-eth0 + ''['' Ethernet = Bridge -a -x /usr/sbin/brctl '']'' + ''['' -n '''' -a -x /sbin/vconfig '']'' + exit 0 ROOT:hex:/tmp]> ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0D:60:C9:52:89 inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:1624 errors:0 dropped:0 overruns:0 frame:0 TX packets:222 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:505277 (493.4 KiB) TX bytes:22079 (21.5 KiB) Base address:0x8000 Memory:c0220000-c0240000 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:1871 errors:0 dropped:0 overruns:0 frame:0 TX packets:1871 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2127980 (2.0 MiB) TX bytes:2127980 (2.0 MiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) ROOT:hex:/tmp]> netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface ROOT:hex:network-scripts]> cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
mylog as your request ifconfig netstat -rn ifdown eth0 netstat -rn ifconfig ***before********** eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B inet addr:172.16.219.40 Bcast:172.16.219.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3989 errors:0 dropped:0 overruns:0 frame:0 TX packets:4719 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:297298 (290.3 KiB) TX bytes:3176564 (3.0 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1768 (1.7 KiB) TX bytes:1768 (1.7 KiB) Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.16.219.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 0.0.0.0 172.16.219.241 0.0.0.0 UG 0 0 0 eth0 **after ifdown eth0 ** Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1768 (1.7 KiB) TX bytes:1768 (1.7 KiB) Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on 2005年8月17日 0:51:>> I, too, am having network related issues. I am now seeing >> this problem on a FC3 box, which previously had worked just >> fine. The networking is working fine before I enter ''xend >> start''. No changes are made to the network-bridge script that >> comes with the source, and the machine has only only nic, eth0. > > Grrr. Please can you do a ''netstat -rn'' before and after. > What kind of network card is this? > > The TX/RX counters for the new eth0 are non zero. Are they going up? > In what whay does networking not work? Can you use tcpdump on eth0 to > determine whether packets from the outside world are arriving. If > not, what about peth0? (Bare in mind that if you only have one-way > connectivity the only packets you''re see are arps, not icmp pings or > anything else) > > Ian > >> ifconfig before ''xend start'': >> >> [root@dbarrera ~]# ifconfig >> eth0 Link encap:Ethernet HWaddr 00:0D:60:F0:C5:C8 >> inet addr:9.53.94.235 Bcast:9.53.94.255 >> Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST >> MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 >> overruns:0 frame:0 TX packets:88 errors:0 dropped:0 >> overruns:0 carrier:0 collisions:0 txqueuelen:1000 >> RX bytes:12299 (12.0 KiB) TX bytes:11426 (11.1 KiB) >> Base address:0x2000 Memory:e8100000-e8120000 >> >> lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) >> >> [root@dbarrera ~]# brctl show >> bridge name bridge id STP enabled interfaces >> [root@dbarrera ~]# >> >> when ''xend start'' is entered, these messages appear on console: >> store_evtchn = 16 XENBUS xs_read_watch: 0 >> >> ifconfig AFTER ''xend start''eth0 Link encap:Ethernet >> HWaddr 00:0D:60:F0:C5:C8 >> inet addr:9.53.94.235 Bcast:9.53.94.255 >> Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST >> MTU:1500 Metric:1 RX packets:380 errors:0 dropped:0 >> overruns:0 frame:0 TX packets:3 errors:0 dropped:0 >> overruns:0 carrier:0 collisions:0 txqueuelen:0 >> RX bytes:28046 (27.3 KiB) TX bytes:426 (426.0 b) >> >> lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> 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:2216 (2.1 KiB) TX bytes:2216 (2.1 KiB) >> >> peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> inet addr:9.53.94.235 Bcast:9.53.94.255 >> Mask:255.255.255.0 UP BROADCAST RUNNING NOARP MULTICAST >> MTU:1500 Metric:1 RX packets:501 errors:0 dropped:0 >> overruns:0 frame:0 TX packets:111 errors:0 dropped:0 >> overruns:0 carrier:0 collisions:0 txqueuelen:1000 >> RX bytes:44601 (43.5 KiB) TX bytes:12036 (11.7 KiB) >> Base address:0x2000 Memory:e8100000-e8120000 >> >> vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:3 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:380 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:426 (426.0 b) TX bytes:28046 (27.3 KiB) >> >> xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:375 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:22208 (21.6 KiB) TX bytes:0 (0.0 b) >> >> [root@dbarrera ~]# brctl show >> bridge name bridge id STP enabled interfaces >> xen-br0 8000.feffffffffff no peth0 >> vif0.0 >> >> xen-br0 is up, but networking is dead. This is different from >> the previous issues where xen-br0 was not coming up, but when >> started manually networking resumed. >> >> On 2 other machines, networking is up and working, Dom0 has >> networking running correctly, but when I start a domU, it >> does not have networking. I have 3 similar machines, only one >> of which has a domU with working network; the other two >> don''t, even though they have very similar setups. This *may* >> end up being a setup issue (although these same setups worked >> before), but I can''t figure out what that could >> be--everything looks like it is supposed to be. >> >>> So, ifdown does succeed in taking the interface down. I >> wander why the routes aren''t getting removed? >>> >>> Could you do: >>> ifconfig >>> netstat -rn >>> ifdown eth0 >>> netstat -rn >>> ifconfig >>> >>> Thanks, >>> Ian >>> >>> >>>> -----Original Message----- >>>> From: Zhai, Edwin [mailto:edwin.zhai@intel.com] >>>> Sent: 16 August 2005 16:57 >>>> To: Ian Pratt >>>> Cc: xen-devel@lists.xensource.com; ian.pratt@cl.cam.ac.uk >>>> Subject: RE: new /etc/xen/network script >>>> >>>> >>>> ***Before*** >>>> [root@vt-edwin ~]# ifconfig >>>> >>>> eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B >>>> >>>> inet addr:172.16.219.31 Bcast:172.16.219.255 >>>> Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST >>>> MTU:1500 Metric:1 >>>> >>>> RX packets:127 errors:0 dropped:0 overruns:0 >>>> frame:0 >>>> TX packets:65 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:1000 >>>> >>>> RX bytes:18387 (17.9 KiB) TX bytes:6072 (5.9 KiB) >>>> >>>> >>>> >>>> lo Link encap:Local Loopback >>>> >>>> inet addr:127.0.0.1 Mask:255.0.0.0 >>>> >>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>> >>>> RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) >>>> >>>> ***After ifdown eth0 *** >>>> [root@vt-edwin ~]# ifconfig >>>> >>>> lo Link encap:Local Loopback >>>> >>>> inet addr:127.0.0.1 Mask:255.0.0.0 >>>> >>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>> >>>> RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) >>>> >>>> >>>> but >>>> [root@vt-edwin ~]# ifconfig -a >>>> eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B >>>> inet addr:172.16.219.31 Bcast:172.16.219.255 >>>> Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 >>>> Metric:1 RX packets:182 errors:0 dropped:0 overruns:0 >>>> frame:0 TX packets:66 errors:0 dropped:0 overruns:0 >>>> carrier:0 collisions:0 txqueuelen:1000 >>>> RX bytes:25284 (24.6 KiB) TX bytes:6196 (6.0 KiB) >>>> >>>> lo Link encap:Local Loopback >>>> inet addr:127.0.0.1 Mask:255.0.0.0 >>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>> RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) >>>> >>>> veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 >>>> BROADCAST MULTICAST MTU:1500 Metric:1 >>>> RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) >>>> >>>> vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >>>> BROADCAST MULTICAST MTU:1500 Metric:1 >>>> RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) >>>> >>>> Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on >>>> 2005年8月16日 23:41: >>>> >>>>>> ian, >>>>>> as the discussion in this thread, service os netwok will break >>>>>> after xend start. this simple patch can work on my mahine. >>>>>> but strange error still occur in xend.log and xend start takes >>>>>> more time with ifdown/ifup. >>>>> >>>>> I guess the patch can''t do any harm, but why doesn''t ifdown >>>>> remove the routes? >>>>> >>>>> Before starting xend, please can you post the output of the >>>>> following sequence: >>>>> >>>>> ifconfig >>>>> ifdown eth0 >>>>> ifconfig >>>>> >>>>> Thanks, >>>>> Ian >>>>> >>>>> >>>>>> @@ -192,6 +192,7 @@ >>>>>> ifconfig p${netdev} -arp down >>>>>> ifconfig p${netdev} hw ether fe:ff:ff:ff:ff:ff >>>>>> ifconfig ${netdev} hw ether ${mac} >>>>>> + del_addrs p${netdev} >>>>>> add_to_bridge ${bridge} vif0.0 >>>>>> add_to_bridge ${bridge} p${netdev} >>>>>> ip link set vif0.0 up >>>>>> >>>>>> >>>>>> --------------xend.log------------------------ >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + set -e [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + OP=start [2005-08-16 23:14:19 xend] ERROR >>>>>> (__init__:988) [network-bridge] + shift [2005-08-16 23:14:19 >>>>>> xend] ERROR (__init__:988) [network-bridge] + for arg in ''"$@"'' >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + export bridge=xen-br0 [2005-08-16 23:14:19 xend] ERROR >>>>>> (__init__:988) [network-bridge] + bridge=xen-br0 [2005-08-16 >>>>>> 23:14:19 xend] ERROR (__init__:988) [network-bridge] + for arg >>>>>> in ''"$@"'' [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + export antispoof=no [2005-08-16 23:14:19 >>>>>> xend] ERROR (__init__:988) [network-bridge] + antispoof=no >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + bridge=xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + netdev=eth0 [2005-08-16 23:14:19 xend] ERROR >>>>>> (__init__:988) [network-bridge] + antispoof=no [2005-08-16 >>>>>> 23:14:19 xend] ERROR (__init__:988) [network-bridge] + echo >>>>>> ''*network start bridge=xen-br0 netdev=eth0 antispoof=no'' >>>>>> [2005-08-16 23:14:19 xend] INFO (__init__:988) [network-bridge] >>>>>> network start bridge=xen-br0 netdev=eth0 antispoof=no >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + case ${OP} in [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + op_start [2005-08-16 23:14:19 xend] ERROR >>>>>> (__init__:988) [network-bridge] + ''['' xen-br0 == null '']'' >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + create_bridge xen-br0 [2005-08-16 23:14:19 xend] ERROR >>>>>> (__init__:988) [network-bridge] + local bridge=xen-br0 >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + brctl show [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + grep -q xen-br0 [2005-08-16 23:14:19 xend] >>>>>> INFO (__init__:988) EVENT> xend.start 0 [2005-08-16 23:14:19 >>>>>> xend] ERROR (__init__:988) [network-bridge] + brctl addbr >>>>>> xen-br0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + brctl stp xen-br0 off [2005-08-16 23:14:19 >>>>>> xend] ERROR (__init__:988) [network-bridge] + brctl setfd >>>>>> xen-br0 0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + ifconfig xen-br0 up [2005-08-16 23:14:19 >>>>>> xend] ERROR (__init__:988) [network-bridge] + ifconfig >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + grep -q veth0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] + ifconfig veth0 [2005-08-16 23:14:19 xend] >>>>>> ERROR (__init__:988) [network-bridge] + grep -q veth0 >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> ++ ifconfig eth0 [2005-08-16 23:14:19 xend] ERROR (__init__:988) >>>>>> [network-bridge] ++ grep HWadd [2005-08-16 23:14:19 xend] ERROR >>>>>> (__init__:988) [network-bridge] ++ sed -e >>>>>> ''s/.*\(..:..:..:..:..:..\).*/\1/'' [2005-08-16 23:14:19 xend] >>>>>> ERROR (__init__:988) [network-bridge] + mac=00:0C:F1:FE:4C:5B >>>>>> [2005-08-16 23:14:19 xend] ERROR (__init__:988) [network-bridge] >>>>>> + ifdown eth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) >>>>>> [network-bridge] + ip link set eth0 name peth0 [2005-08-16 >>>>>> 23:14:20 xend] ERROR (__init__:988) [network-bridge] + ip link >>>>>> set veth0 name eth0 [2005-08-16 23:14:20 xend] ERROR >>>>>> (__init__:988) [network-bridge] + ifconfig peth0 -arp down >>>>>> [2005-08-16 23:14:20 xend] ERROR (__init__:988) [network-bridge] >>>>>> + ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff [2005-08-16 23:14:20 >>>>>> xend] ERROR (__init__:988) [network-bridge] + ifconfig eth0 hw >>>>>> ether 00:0C:F1:FE:4C:5B [2005-08-16 23:14:20 xend] ERROR >>>>>> (__init__:988) [network-bridge] + del_addrs peth0 [2005-08-16 >>>>>> 23:14:20 xend] ERROR (__init__:988) [network-bridge] + local >>>>>> src=peth0 [2005-08-16 23:14:20 xend] ERROR (__init__:988) >>>>>> [network-bridge] + ip addr show dev peth0 [2005-08-16 23:14:20 >>>>>> xend] ERROR (__init__:988) [network-bridge] + egrep ''^ *inet '' >>>>>> >>>>>> Best Rgds >>>>>> Edwin >>>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> -- >> Regards, >> >> David F Barrera >> Linux Technology Center >> Systems and Technology Group, IBM >> >> "The wisest men follow their own direction. " >> Euripides_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> -----Original Message----- > From: Nivedita Singhvi [mailto:nsnix@comcast.net] > Sent: 17 August 2005 13:12 > To: Ian Pratt > Cc: Ian Pratt; xen-devel@lists.xensource.com; Zhai, Edwin > Subject: Re: [Xen-devel] RE: new /etc/xen/network script > > Ian Pratt wrote: > > >>Guh. ifdown doesn''t delete the addrs, and once they are, via > >>del_addrs, the link up doesn''t result in route creation.> > What''s the contents of your ifcfg-eth0 file? (you may have multiple > > under different profiles)> FC3. > Not setting address via kernel cmd line.So, it looks like the ''active ingredient'' of ''ifdown eth0'' is the following line: ip link set dev eth0 down Somehow, this seems to remove the ipv6 address, but leave the ipv4 one. I guess an ''ifconfig eth0 0.0.0.0'' is a reasonable way to clear out the ipv4 address. I''ve checked something in. Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhai, Edwin wrote:> mylog as your request > ifconfig > netstat -rn > ifdown eth0 > netstat -rn > ifconfig >Edwin, could you post your ifconfig -a output (which displays *all* interfaces, even those currently in DOWN state)? Also, if you are able to test on a xen box, could you run through the xend start and see the output of network-bridge in xend.log and also check netstat -rn at the end? thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:> I guess an ''ifconfig eth0 0.0.0.0'' is a reasonable way to clear out the > ipv4 address. > > I''ve checked something in. > IanThanks, Ian. We''ll test later today. thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
ian, should remove "-x" in the first line of the script, else the debug output will cause a lot of xend errors. thanks Ian Pratt <mailto:m+Ian.Pratt@cl.cam.ac.uk> scribbled on 2005年8月17日 20:35:>> -----Original Message----- >> From: Nivedita Singhvi [mailto:nsnix@comcast.net] >> Sent: 17 August 2005 13:12 >> To: Ian Pratt >> Cc: Ian Pratt; xen-devel@lists.xensource.com; Zhai, Edwin >> Subject: Re: [Xen-devel] RE: new /etc/xen/network script >> >> Ian Pratt wrote: >> >>>> Guh. ifdown doesn''t delete the addrs, and once they are, via >>>> del_addrs, the link up doesn''t result in route creation. > >>> What''s the contents of your ifcfg-eth0 file? (you may have multiple >>> under different profiles) > >> FC3. >> Not setting address via kernel cmd line. > > So, it looks like the ''active ingredient'' of ''ifdown eth0'' is the > following line: > ip link set dev eth0 down > > Somehow, this seems to remove the ipv6 address, but leave the ipv4 > one. > > I guess an ''ifconfig eth0 0.0.0.0'' is a reasonable way to clear out > the ipv4 address. > > I''ve checked something in. > Ian_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
********* my log for "ifdown eth0"************ [root@vt-edwin ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B inet addr:172.16.219.40 Bcast:172.16.219.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:549 errors:0 dropped:0 overruns:0 frame:0 TX packets:609 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45029 (43.9 KiB) TX bytes:439428 (429.1 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) [root@vt-edwin ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.16.219.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 0.0.0.0 172.16.219.241 0.0.0.0 UG 0 0 0 eth0 [root@vt-edwin ~]# ifdown eth0 [root@vt-edwin ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface [root@vt-edwin ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0C:F1:FE:4C:5B inet addr:172.16.219.40 Bcast:172.16.219.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:771 errors:0 dropped:0 overruns:0 frame:0 TX packets:651 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:68492 (66.8 KiB) TX bytes:444728 (434.3 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16 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:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB) veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) ****info after xend start****** xend.log pls. see attachent file. [root@vt-edwin log]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.16.219.0 0.0.0.0 255.255.255.0 U 0 0 0 peth0 172.16.219.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 0.0.0.0 172.16.219.241 0.0.0.0 UG 0 0 0 peth0 peth0 shold not in the route table. Nivedita Singhvi <mailto:nsnix@comcast.net> scribbled on 2005年8月17日 20:35:> Zhai, Edwin wrote: >> mylog as your request >> ifconfig >> netstat -rn >> ifdown eth0 >> netstat -rn >> ifconfig >> > > Edwin, could you post your ifconfig -a output > (which displays *all* interfaces, even those currently > in DOWN state)? > > Also, if you are able to test on a xen box, could > you run through the xend start and see the output > of network-bridge in xend.log and also check netstat -rn > at the end? > > thanks, > Nivedita_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 2005-08-17 at 05:37 -0700, Nivedita Singhvi wrote:> Ian Pratt wrote: > > > I guess an ''ifconfig eth0 0.0.0.0'' is a reasonable way to clear out the > > ipv4 address. > > > > I''ve checked something in. > > Ian > > Thanks, Ian. We''ll test later today.I am assuming the new network-bridge script is in the latest hg pull as of this morning. It seems to have fixed the problems on the SLES 9 boxes; however, I seem to be having trouble on the FC3/4 boxes; the domUs on those boxes cannot connect to the network, even though they seem to be setup correctly and both worked previously. One has a static IP address, and the other is setup for dhcp.> > thanks, > Nivedita > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> > Thanks, Ian. We''ll test later today. > I am assuming the new network-bridge script is in the latest > hg pull as of this morning. It seems to have fixed the > problems on the SLES 9 boxes; however, I seem to be having > trouble on the FC3/4 boxes; the domUs on those boxes cannot > connect to the network, even though they seem to be setup > correctly and both worked previously. One has a static IP > address, and the other is setup for dhcp.It works on FC3 OK for me. Please post the xend.log Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 2005-08-17 at 17:34 +0100, Ian Pratt wrote:> > > Thanks, Ian. We''ll test later today. > > I am assuming the new network-bridge script is in the latest > > hg pull as of this morning. It seems to have fixed the > > problems on the SLES 9 boxes; however, I seem to be having > > trouble on the FC3/4 boxes; the domUs on those boxes cannot > > connect to the network, even though they seem to be setup > > correctly and both worked previously. One has a static IP > > address, and the other is setup for dhcp. > > It works on FC3 OK for me.Well, on the FC4 box, I rebooted Dom0 and created a DomU without changing anything, and now DomU has network working. Don''t know what was different this time, but it is working. So, I have 2 SLES 9 SP2 boxes and an FC4 box booted to Dom0 and with functional DomUs now. The FC3 is the dhcp box, and maybe the dhcp server is out of addresses.> > Please post the xend.log > > Ian >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel