When adding an Cluster Managed Virtual Machine (VM) Service, rgmanager currently restarts the VM as it does with other managed services. This is likely to be an unexpected event for a running virtualized OS instance. Instead, for managing VM's we need to leave a running VM running.
This is a trivial fix. Services which are tagged as migratory (e.g. they have the 'migrate' action and have no children) can be ignored in do_condstops / do_condstarts. The next question is: Do we stop the VM if you delete it from the cluster config or not?
in answer to "Do we stop the VM if you delete it from the cluster config or not? " The answer is no. Changing the management of the VM should not cause it to restart.
Created attachment 160273 [details] Patch This implements the required behavior and minimizes virtual machine transitions. If added or removed from the cluster configuration, virtual machines no longer transition (though if desired, this can be altered). Additionally, if non-critical attributes of the virtual machine are altered, the virtual machine is not restarted. This patch has the side effect of fixing #247801.
Created attachment 160275 [details] Cleaned up patch
*** Bug 247801 has been marked as a duplicate of this bug. ***
Patches in CVS
On a node reboot, the guest correctly gets restarted on another node. However, once the node returns, rgmanager stops the guest and restarts it on the recovery node. Either it should use live migration to return it or leave it on the failover node. Setting to fails-qa
Rob, I checked in more patches for this before going on vacation - it should be working now. It's on your cluster. Could you retest?
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0580.html