Red Hat Bugzilla – Bug 383071
Virtual machine configuration - add field for "migration type" xml attr = "migrate"
Last modified: 2009-04-16 18:44:04 EDT
+++ This bug was initially created as a clone of Bug #345871 +++
Currently, the live migration of instances through rgmanager (and Conga), the OS
instance will pause, migrate and then continue. This can be changed by editig
the vm.sh file and adding "-l" to the migration command.
We should make "-l" style migration the default to avoid the pause timing out
-- Additional comment from firstname.lastname@example.org on 2007-11-14 13:59 EST --
Patch in CVS:
Synopsis: migrate attribute for vm configuration
Possible values: live or pause, default=live
<vm name="molly" migrate="pause"/> <--- "xm migrate molly..."
<vm name="frederick" migrate="live"/> <--- "xm migrate -l frederick..."
<vm name="buster"/> <--- "xm migrate -l buster..."
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Actually, I do need more info for proper testing.
Should conga auto-detect that hosts are xen vms, and then generate the above
like in /etc/cluster/cluster.conf after only adding the virtual hosts (or
This is for manual configuration of VM services (to be managed by rgmanager).
The functionality added is letting users choose whether migration type should be
live or pause. You can get to the form via cluster -> [cluster name] -> services
-> Add a Virtual Service. Or you can modify an existing one to get to the same
looks sane across several passes, changing to verified.
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 therefore 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.