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

10.3.3.5 Marking a Guest Not Runnable
On all VM Hosts that have a virtual machine configured, the virtual machine should be marked
Runnable on only one VM Host at a time. While migrating online guests, unexpected errors or
guest resets or aborts should not cause your guest to be marked Runnable or Not Runnable
incorrectly.
To verify the Runnable state of a virtual machine, use the hpvmstatus command to see that
the guest is Runnable on only one VM Host and Not Runnable on all other VM Hosts. If the
Runnable state of a virtual machine is not correct on a VM Host, use the hpvmmodify command
to correct it.
For information about the hpvmmodifycommand and how to mark a guest Runnable or Not
Runnable, see Section 10.2.4 (page 173).
To mark a guest Not Runnable, use the following command:
# hpvmmodify -P guestname -x runnable_status=disabled
To mark a guest Runnable, use the following command:
#hpvmmodify -P guestname -x runnable_status=enabled
WARNING! Be very careful when marking a guest Runnable when it was previously Not
Runnable. Make sure this guest is Not Runnable and definitely not actually running on any
other VM Host.
10.3.4 Restrictions and Limitations of Online VM Migration
Administrators should carefully configure certain aspects of VM Hosts and guests for online
migration capability. Integration with automated workload placement, management and load
balancing tools are not supported in this release. Only Integrity VM command-line interfaces
are available in V4.2. More automated and more convenient management of distributed Integrity
VM guests might follow in subsequent Integrity VM releases.
A dedicated high-speed network should not be on the data center, work site, company, or “public”
LAN. Because online migration does not encrypt the data, using a private connection ensures
secure transfer of guest memory and state. Online migration can also swamp the network while
a migration is in progress. Using the site's network for migration traffic would also create peaks
of network activity that might affect network performance. Using a high-speed network is
desirable to minimize guest memory transfer time and allows your guest to migrate smoothly.
Only whole disk backing storage consisting of SAN LUNs, and ejected file-backed DVDs, are
supported for guest storage if you plan to migrate the guest online. File and logical volume
backing storage are not supported for online guest migration.
Only one online migration to or from a VM Host can be performed at a time. Also, be aware of
the state of the guest while migrating it online. If the guest is in the On (EFI) state and no guest
operating system is booted, the online migration fails with an error. If the guest is shutting down,
restarting or crashing while migrating, the online migration aborts when the hpvmmigrate
command can no longer communicate with the guest.
NOTE: Integrity VM supports SLVM backing storage for online migrations. For details about
shared LVM (SLVM) storage, see Section 11.5 (page 200).
10.4 Migrating Serviceguard Packaged Guests and Serviceguard Cluster
Nodes
In a Serviceguard cluster, you can use hpvmsg_move to migrate a packaged guest online. For
example, to migrate the packaged guest ogmlin to node2, use the hpvmsg_move command as
follows:
10.4 Migrating Serviceguard Packaged Guests and Serviceguard Cluster Nodes 181