VCS requirements:
Verify that the value of IntentionalOffline attribute for HPVirtualMachine type is set to 1. (The default value is 1.)
Make sure that the HPVirtualMachine resource for the VMGuest that you plan to migrate is in a steady state OFFLINE or ONLINE.
To rename the VMGuest when you migrate it, make sure that the VMName attribute for the HPVirtualMachine resource in VCS is localized with the target VMGuest name for the target VMHost system. When you rename it, VCS can continue to monitor the renamed VMGuest after migration.
IVM Requirements:
Enable password-less SSH between source and target hosts for superuser.
Make sure that you do not create VMGuest on the target VMHost if you are migrating for the first time.
The source VMHost and the target VMHost must be running Integrity VM (IVM) and must be able to run the guests.
Both machines must be able to provide the allocated resources to the guest. For example, if the guest uses 2-GB memory on one machine, it must be able to use the same amount of memory on the other machine. Similarly, if the source machine can provide a guest with four vCPUs, then the target machine must also be able to provide the same number of vCPUs.
All resources used by the guest must be configured symmetrically on both the source and target VMHosts. A symmetric configuration includes:
Refer to the following references in HP Integrity VM documentation for more information:
For more details on migration requirments refer to Migrating Virtual Machines of HP Integrity Virtual Machines Installation, Configuration and Administration guide.
For IVM Installation Requirements refer to Installation Requirements of HP Integrity Virtual Machines Installation, Configuration and Administration guide.