HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

Online migration support among Integrity servers is limited by the processor architecture. Online
migration among servers with processor family 31 is supported regardless of the model number
within that family. Migration among servers with processor family 32 and model numbers 0 or
1 is supported. Otherwise, online migration is supported among servers with identical processor
family and model number.
To check if a guest can be migrated to the target VM Host, use the -s option to the hpvmmigrate
command.
NOTE: Integrity VM supports SLVM backing storage for online migrations. For details about
shared LVM (SLVM) storage, see migratingVMs.
Veritas volumes are not supported for Online VM Migration.
9.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:
# hpvmsg_move -n node2 ogmlin
The Integrity VM V4.3 hpvmsg_move command disables the package before migrating the
guest and re-runs the package after migration is finished. Therefore, the packaged guest is not
protected by Serviceguard while migration is in progress.
A guest configured as a Serviceguard package is not protected by Serviceguard while the migration
is in progress. The hpvmsg_move command temporarily disables package failover prior to the
migration and re-enables package failover after migration has completed. If a failure occurs
during the migration process, you must re-enable package failover manually and restart the
guest by running it on one of the Serviceguard cluster nodes.
For example, to disable 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.
The hpvmsg_move command is used to initiate online migrations of Serviceguard guest packages.
This command is located in the /opt/cmcluster/toolkit/hpvm directory, which is not
added to the users PATH variable during installation. To initiate an online migration, use the
full pathname to the hpvmsg_move command. The full pathname to the command is: /opt/
cmcluster/toolkit/hpvm/hpvmsg_move
9.5 Migrating Guests from Physical to Virtual Machines
The P2V assistant is a menu driven utility that helps you consolidate or migrate between systems.
The source and target systems can actually be either virtual systems or physical systems, as the
feature is implemented as a general purpose utility. To use the P2V assistant, enter the p2vassist
command on the VM Host.
9.5.1 Requirements for Migrating a Workload
The Integrity VM software must be installed on the source system. The source system and target
system must have SSH connectivity. You can connect from the VM Host system to the target
server without a password (host-based authentication).
The P2V assistant migrates only applications that have Software Depot (SD) packages. Applications
that are not SD compliant cannot be migrated with the P2V assistant.
194 Migrating Virtual Machines