On May 28, 2009, at 9:16 PM, Fajar A. Nugraha wrote:
On Fri, May 29, 2009 at 3:55 AM, Mike Brady
That would be because both Xen and RHEL/Centos are broken when it
to bonded bridged interfaces.
Apply the patch from https://bugzilla.redhat.com/show_bug.cgi?
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
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
Putting the following options under /etc/modprobe.conf takes care of
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
(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.
Description: S/MIME cryptographic signature
Xen-users mailing list