On Fri, 12 Oct 2012 09:22:13 +0200 Florian Haas <flor...@hastexo.com> wrote: > For most people, this issue doesn't occur on system boot, as libvirtd > would normally start before corosync, or corosync/pacemaker isn't part > of the system bootup sequence at all (the latter is preferred for > two-node clusters to prevent fencing shootouts in case of cluster > split brain).
Hm, here I start libvirt (as clone-resource) from pacemaker and don't have such problems. But fi I remember correctly I have a) both order and location constraints for the VMs to libvirtclone, b) location-constraints to pingd-value and c) my own RA for virtual machine that reacts differently when libvirtd isn't started yet. But I also had to restore a vm from backup when an os-update stopped (and didn't restart) libvirtd and pacemaker started a second instance of the machine on a different host. Now I think I remember to put nodes to standby-mode before doing upgrades of core-components... <snip> > Also, a running libvirtd is not > needed, to the best of my knowledge, when the hypervisor in use is Xen > rather than KVM. With KVM you can also start virtual machine without libvirtd. You just have to use qemu-kvm and a lot of commandline parameters. Have fun, Arnold
signature.asc
Description: PGP signature
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
