diff options
author | Keir Fraser <keir.fraser@citrix.com> | 2009-10-14 09:09:23 +0100 |
---|---|---|
committer | Keir Fraser <keir.fraser@citrix.com> | 2009-10-14 09:09:23 +0100 |
commit | b1fd365cece2833c767ee8f96c421ee32e467af5 (patch) | |
tree | 9697a4c1ff1bb94d6d192b772daa3853149f5b1f /stubdom/stubdom-dm | |
parent | 11a92ae1f0692109990da8e34e945c298afb4c6f (diff) | |
download | xen-b1fd365cece2833c767ee8f96c421ee32e467af5.tar.gz xen-b1fd365cece2833c767ee8f96c421ee32e467af5.tar.bz2 xen-b1fd365cece2833c767ee8f96c421ee32e467af5.zip |
xm,xend: Add new option "change_home_server" to xm migrate
This patch adds a new option to xm migrate command. A concept of the
option is inspired from XenServer/XenCenter. The concept is "Change
home server (affinity)." The option name is "change_home_server."
Currently, a config.sxp file of a managed domain is not migrated to a
destination server even if the migration of the managed domain
succeeds. The config.sxp file is kept in a source server.
By the patch, the config.sxp file is migrated with the managed domain.
The config.sxp file is unregistered from the source server, then the
config.sxp file is registered to the destination server.
BTW, should the config.sxp file be always migrated without the option?
If the managed domain is migrated without the option, the managed
domains exist on both the source server and the destination server.
(Of course, the managed domain on the source server is "halted" state,
and the managed domain on the destination server is "running" state.)
Is it good that the managed domains with a same UUID exist on both
servers? (In the patch, I added the option for compatible.)
Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Diffstat (limited to 'stubdom/stubdom-dm')
0 files changed, 0 insertions, 0 deletions