HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

5. If migrating the guest offline, restart the guest on the target host using the hpvmstart or
hpvmconsole command. You can also use the hpvmmigrate -b option with an offline
migration to automatically restart the guest on the target.
6. If you do not use the hpvmmigrate -D option to remove the virtual machine configuration
on the source VM Host, it is marked Not Runnable, and it is configured with all its devices.
This protects the storage from unintended use by Integrity VM commands.
If you never intend to migrate the guest back to the source VM Host, you can remove the
virtual machine configuration with the hpvmremove command. Once the guest is removed
from the VM Host, you should unpresent the guest's SAN storage and remove the associated
device special files (using the rmsf command). Or, if you cannot unpresent the storage, you
should use the hpvmdevmgmt -a rdev:/device command for each device to mark them
restricted.
The hpvmmigrate command verifies that the target host has sufficient resources (such as
memory, network switches and storage devices) for the guest to run. If the resources are
insufficient or do not exist, or if other errors occur, the guest is not migrated to the target host.
After successfully migrating the guest, the hpvmmigrate command automatically disables the
guest on the source host.
10.2.1 Using the hpvmmigrate Command
Use the hpvmmigrate command to move an online guest or an offline virtual machine from a
source VM Host to a specified target VM Host. Virtual machines can be migrated while OFF,
and online guests can be migrated while ON and running. Use the -o option to migrate an online
guest, which involves copying all the virtual machine's configuration information and transferring
the active guest memory and virtual CPU state. Omit the -o option to migrate just the offline
virtual machine's configuration information, and optionally local disk contents, to the target VM
Host.
The resources that are defined in the virtual machine's configuration information are checked
to determine whether the migrated virtual machine can boot on the target VM Host. If there is
a problem, it is reported, and the virtual machine is not migrated. You can specify the -F option
(force) to suppress the errors and force the virtual machine migration to the target VM Host.
CAUTION: Use the -F option with caution, because some errors can prevent a virtual machine
from working properly on the target VM Host.
By default, Integrity VM retains the virtual machine configuration and marks it Not Runnable
(NR) on the source VM Host after it is migrated successfully to the target VM Host. Run the
hpvmstatus command to see that the state of the virtual machine is now Off(NR) on the source
VM host and the guest is On(OS) on the target VM Host. The guest is running on the target VM
Host and is, therefore, considered Runnable.
This mechanism allows the same virtual machine to be configured on multiple VM Hosts, while
still preventing accidental booting of the same guest on multiple hosts simultaneously. Each
virtual machine must be Runnable on only one VM Host at any given time to prevent the
possibility of two virtual machines using the same SAN storage at the same time. Use the
hpvmmodify command, if necessary, to mark the virtual machine Runnable on only the VM
Host, and Not Runnable on all other hosts that know about that virtual machine configuration
information.
NOTE: Mark a migrated virtual machine as Runnable only in rare circumstances and with
great care. Inappropriate use can cause disk corruption.
When you invoke the hpvmmigrate command, you must specify the name of the guest to be
migrated and the target VM Host system.
10.2 Command Line Interface for Online and Offline Migration 169