WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] CentOS 5.3 bond0 and xen 3.3.0

On Fri, 2009-05-29 at 09:31 -0400, Adam Wead wrote:
> On May 28, 2009, at 9:16 PM, Fajar A. Nugraha wrote:
> 
> > On Fri, May 29, 2009 at 3:55 AM, Mike Brady  
> > <mike.brady@xxxxxxxxxxxxxx> wrote:
> >>
> >> That would be because both Xen and RHEL/Centos are broken when it  
> >> comes
> >> to bonded bridged interfaces.
> >
> >> Apply the patch from https://bugzilla.redhat.com/show_bug.cgi? 
> >> id=463014
> >
> > Thanks for the info. I have a similar setup, but strangely enough it
> > works without any need for patch.
> > Perhaps its because I'm using bridging on top of vlan on top of  
> > bonding.
> >
> 
> Mine works as well too, under Red Hat EL5, but I don't use any config  
> file under sysconfig to create the bridge or any vlan either.  This  
> may be why this bug didn't' affect me.  Instead I have Red Hat only  
> create the bond device from the 2 interfaces, and have Xen create the  
> bridge:
> 
> /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE=eth0
> TYPE=Ethernet
> USERCTL=no
> ONBOOT=yes
> BOOTPROTO=none
> IPV6INIT=no
> PEERDNS=no
> HWADDR=00:1A:64:09:26:F4
> MASTER=bond0
> SLAVE=yes
> 
> /etc/sysconfig/network-scripts/ifcfg-eth1
> DEVICE=eth1
> TYPE=Ethernet
> USERCTL=no
> ONBOOT=yes
> BOOTPROTO=none
> IPV6INIT=no
> PEERDNS=no
> HWADDR=00:1A:64:09:26:F6
> MASTER=bond0
> SLAVE=yes
> 
> /etc/sysconfig/network-scripts/ifcfg-bond0
> DEVICE=bond0
> BOOTPROTO=none
> ONBOOT=yes
> USERCTL=no
> IPV6INIT=no
> PEERDNS=no
> IPADDR=10.79.184.5
> NETMASK=255.255.255.0
> GATEWAY=10.79.184.254
> 
> Putting the following options under /etc/modprobe.conf takes care of  
> the rest:
> alias bond0 bonding
> options bonding miimon=100 mode=0
> 
> Then, Xen creates the bridge to bond0 under /etc/xen/xend.cfg
> (network-script 'network-bridge netdev=bond0')
> 
> and then creates pbond0, and xenbr0
> 
> The only problem I'm having with this setup is that I can apparently  
> only attach one guest to xenbr0.  If I attach a second, it's network  
> connectivity is unstable and it's inaccessible over the network.   
> However, the setup works great for one guest: you can unplug either  
> NIC and the network stays up.
> 
> There is a network-bridge-bonding script under /etc/xen/scripts that  
> would seem to address everyone's needs.  I tried to use it under  
> xend.cfg:
> (network-script 'network-bridge-bonding netdev=bond0')
> 
> But could never get it to work...
> 
> I'd like to find out to attach multiple guests to a bonded device,  
> but don't have an extra multi-NIC system handy to play with.  I'd  
> appreciate hearing you all's views on this.
> 
> best,
> 
> ...adam
> 
> 
> 

Which Xen and therefore network-bridge script are you running?

Your configuration will work with Red Hat's network-bridge script.  The
default Xen script takes the interface down (in this case bond0) when
it is moving the addresses etc around, which breaks the bond.  The Red
Hat network-bridge script doesn't take the interface down if is a
bond.  I was doing things the way you are when I was using the Red Hat
Xen packages.  When I moved to the gitco packages (which has the
standard Xen network-bridge script) I changed to what I have previously
indicated.

I currently only have 3 DomUs using the bridge, but have had more in
the past with no networking issues.


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