This section explains how to migrate a VM guest to a VM host on a different physical server.
Two methods of VM guest migration are available in Resource Coordinator VE. Although such methods are named differently depending on the virtualization software used, Resource Coordinator VE makes use of the following naming convention.
For details on migration pre-requisites and terminology, refer to "A.3 Functional Differences between Products" in the "ServerView Resource Coordinator VE Setup Guide".
Live migration: migration of a VM guest without shutting down its VM host
Cold migration: migration of a VM guest while its VM host is shut down.
Availability of those methods depends on the power state of VM guests, as described below.
VM Guest Power State | Migration Form | |
---|---|---|
Cold Migration | Live Migration | |
ON | Available | Default |
OFF | Default | N/A |
Default: This method is available and selected by default.
Available: This method is available.
N/A: This method is not available.
A VM guest after migration is set to the same power state as it was before the migration. For example, performing a cold migration on an operating VM guest will temporally shut it down during migration, before starting it up again after completion of the migration process. It is therefore recommended to set the target VM guest in the desired post-migration state before starting a migration.
VM guests can be migrated from the command-line, using the "rcxadm server migrate" command. Refer to "3.2 rcxadm server" in the "ServerView Resource Coordinator VE Command Reference" for details.