On 31/08/2010, at 2:54 AM, Jeff Sturm wrote: > > The network-bridge script does some pretty horrific things to networking while it starts. I’m not surprised if the interruption is enough to cause CMAN to fail. > > We avoided this by not using Xen’s network-bridge utility. Just configure your physical interfaces and bridge devices in /etc/sysconfig/network-scripts, and specify a bridge name in each /etc/xen/<domU> script. (In xend-config.sxp you can set network-script to “/bin/true”. Just remember to also turn on IP forwarding.) > > The advantages of doing it this way are that you get tighter control over your host networking, and starting/stopping xend won’t interrupt networking. (The main disadvantage is that the networking configuration is harder to port to a non-Red Hat OS, but if you already need clustering that probably doesn’t matter.) For what it's worth, we do the same thing. Set network-script to /bin/true in xend-config.sxp and configure our own bridges via regular ifcfg scripts in /etc/sysconfig/network-scripts/. Much more stable and predictable this way. -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
