HP Integrity Virtual Machines Version 4.2 Release Notes

9.2.3 NR Guest State
A guest is placed in the Not Runnable (NR) state when it is the source of a successful migration.
The guest is also marked Not Modify and Not Visible. The guest can also be placed in the NR
state by the administrator using thehpvmmodify command, for example:
# hpvmmodify -P guestname -x register_status=disabled
The NR guest state appears on the hpvmstatus command output as Off (NR).
CAUTION: Use of the -x register_status option is highly discouraged and may lead to
accidentally booting a VM on more than one host at once.
NOTE: The -x register_status option has replaced the -x runnable_status status
on the hpvmmodify command line, as changing register_status now affects
runnable_status, modify_status and visible_status.
9.2.4 A Guest Might be Marked Disabled After Failed Offline Migration
It is rare but possible that a guest is marked Not Runnable after a failed offline migration. If this
occurs, use the following command to return the guest to the registered state:
# hpvmmodify -P guestname -x register_status=enabled
Before enabling the guest on the source, check the target to ensure that the guest was not actually
migrated there.
9.2.5 Do Not Migrate Serviceguard Cluster Nodes
Online VM Migration does not support migrating guests that are Serviceguard cluster nodes. If
a Serviceguard node is migrated while online, it might lose connection to other cluster members
and be automatically removed from the cluster.
The Integrity VM software does not know whether you have installed Serviceguard in a guest,
so it cannot automatically restrict online migration of your Serviceguard node. Therefore, you
should disable online migration for all Serviceguard nodes. For example, to disable Online VM
Migration for the guest sgnode, run the hpvmmodify command as follows:
# hpvmmodify -P sgnode -x online_migration=disabled
Disabling online migration for the guest ensures that you do not accidentally attempt to migrate
a Serviceguard node.
9.2.6 Unpresenting SAN Devices to Integrity VM Hosts
Unpresenting SAN devices that were configured to be used by guests causes the guest to fail to
start. If SAN devices must be unpresented, guests configured to use those devices should be
reconfigured to no longer require them. After unpresenting a device special file, remove it from
the Integrity VM Host using the following command:
rmsf –a device_special_file
The device special file can be derived from the wwid_string, obtained from the SAN appliance,
as follows:
scsimgr -p get_attr -a wwid -a device_file current all_lun | grep wwid_string
9.2.7 Host May Participate in Only One Online Migration at a Time
A VM Host may participate in one online migration at a time, either as a source or a target. If
two migrations are attempted at the same time, hpvmmigrate might fail quickly with an error.
However, hpvmmigrate does not always detect that a migration is in progress.
84 Migrating Virtual Machines