Building a pacemaker cluster to manage Xen domU virtual machines the sysadm can choose between to different resource agents:
- the dedicated Xen resource agent (ocf:heartbeat:Xen)
- the libvirt based resource agent (ocf:heartbeat:VirtualDomain)
Both will support the usual start/stop operations and live migration between running nodes. The Xen ra implements the monitor action by running xm list (which I do know can be really slow sometime, leading to problems if the monitor timeout is set too low), the libvirt one uses virsh domstate (which I don't know how it is implemented).
Overall, the two RA seem to be nearly identical in features.
Is there any reason to prefer one resource type over the other when planning and implementing a new cluster?