HP Integrity Virtual Machines 4.2.5: Release Notes

Can't open VM /var/opt/hpvm/uuids/c0c8a8ee-ac67-11dd-ba00-00306ef3bda7/vm_dev:
(55) VMM not loaded
Opening minor device and creating guest machine container
Creation of VM, minor device 1
hpvmmigrate: ERROR (vmname): Remote message: Target guest exited. Status 2.
hpvmmigrate: ERROR (vmname): Remote message: Unable to start guest on target.
In this case, use the following workaround:
1. Enter the following:
# swremove vmOVMMSW.OnlineMigr-SW
2. Force a reinstall of the 4.1 stack by forcing a reinstall of the T8718AC bundle:
# swinstall -x autoreboot=true -x reinstall=true -s T8718AC
Note, this reinstall reboots the VM Host.
You might receive the following message after specifying the hpvmmigrate command:
Host is not licensed for online migration.
In this case, the workaround is to install the Online VM Migration bundle, T8718AC from the AR.
9.2.4 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 the hpvmmodify 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.5 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.6 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.
90 Migrating Virtual Machines