On 20 Dec 2013, at 5:30 am, Bob Haxo bh...@sgi.com wrote:
Hello,
Earlier emails related to this topic:
[pacemaker] chicken-egg-problem with libvirtd and a VM within cluster
[pacemaker] VirtualDomain problem after reboot of one node
My configuration:
Hi Andrew,
With configuration fumble, err, test, that brought about this of
chickens and eggs and VMs request, the situation is that the reboot of
the non-host server results in the restart of the VM running on the host
server.
From earlier [Pacemaker] thread:
From: Tom Fernandes
Hello,
Earlier emails related to this topic:
[pacemaker] chicken-egg-problem with libvirtd and a VM within cluster
[pacemaker] VirtualDomain problem after reboot of one node
My configuration:
RHEL6.5/CMAN/gfs2/Pacemaker/crmsh
pacemaker-libs-1.1.10-14.el6_5.1.x86_64
if don't set your vm to start at boot time, you don't to put in cluster
libvirtd, maybe the problem isn't this, but why put the os services in
cluster, for example crond .. :)
2013/12/19 Bob Haxo bh...@sgi.com
Hello,
Earlier emails related to this topic:
[pacemaker] chicken-egg-problem
Maybe the problem is this, the cluster try to start the vm and libvirtd
isn't started
2013/12/19 emmanuel segura emi2f...@gmail.com
if don't set your vm to start at boot time, you don't to put in cluster
libvirtd, maybe the problem isn't this, but why put the os services in
cluster, for
Hi Emmanuel,
Thanks for the suggestions. It is pretty clear what is the problem; it's
just not clear what is the fix or the work-around.
Search the Pacemaker email archive for the email of Andrew Beekhof, 12
Oct 2012, Re: [Pacemaker] chicken-egg-problem with libvirtd and a VM
within cluster,
remove the libvirtd from pacemaker and chkconfig libvirtd on every node,
like that the cluster just manage the vm, maybe i wrong but i don't see any
reason for put libvirtd as primitivi in pacemaker
2013/12/19 Bob Haxo bh...@sgi.com
Hi Emmanuel,
Thanks for the suggestions. It is pretty
Hi Emmanuel,
i don't see any reason for put libvirtd as primitive in pacemaker
Yes ... well, maybe. During my testing of failure scenarios (in
particular, reboot of the VM host), several times the VM filesystem
ended up corrupted and I needed to reinstall the VM. At least a couple
of these
