[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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@xxxxxxxxxxxxxxxxxxx 
> 
>                               08/11/2005 12:36 PM
> 
> 
> 
> To
> 
> "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>        
> 
> 
> cc
> 
> xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, 
> xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> 
> 
> 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@xxxxxxxxxxxx>"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
> 
> 
> 
>                                                               
> "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx> 
> 
>                                                               
> 08/11/2005 04:27 AM
> 
> 
> To
> 
> Li Ge/Austin/IBM@IBMUS        
> 
> cc
> 
> "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, 
> <xen-devel-bounces@xxxxxxxxxxxxxxxxxxx>, <ian.pratt@xxxxxxxxxxxx>     
> 
> 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@xxxxxxxxxxxx>"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
> > 
> > 
> > 
> > 
> > "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx> Sent by:
> > xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > 
> > 08/09/2005 07:58 PM
> > 
> > 
> > 
> > To
> > 
> > "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
> > 
> > 
> > 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@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel 
> > <http://lists.xensource.com/xen-devel>
> > 
> > 
> > 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.