On Wed, 2013-01-09 at 13:15 +1100, Andrew Beekhof wrote: > IIRC, part of the activation involves tearing down the "normal" > interface and creating the bridge. > At this point the device heartbeat was talking to is gone.
I hadn't thought of that, because afterwards, ethX looks exactly the same as it did before, same IP and other settings. It just has xenbrX attached to it. But I admit I don't know exactly what happens there. > > > I got the cluster running with xend by > > moving the heartbeat to a different interface. > > Having heartbeat start after the bridge is created _should_ also work. Obviously that can't work if xend is a cluster resource. I suppose xend could be started outside the cluster before heartbeat, but then I don't get to have it monitored by Pacemaker. So this will be in the archives as a warning to people running clusters for Xen virtual machines (or anything else that sets up bridged networking). In my case, the only solution is to use an interface for heartbeat that is not touched by Xen networking. I suppose people who are using something other than bridged networking may not have this issue either. --Greg _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
