HP Integrity Virtual Server Manager 6.3 User Guide

Serviceguard requirements and recommendations
For online migration of a VM configured as a Serviceguard package, package switching for the
migrating VM guest package is disabled before migration begins and then re-enabled immediately
after the migration finishes. Therefore, the VM software is not protected by Serviceguard during
the migration process. If a failure occurs during migration, you must manually re-enable package
failover after the migration completes and restart the VM by running it on one of the Serviceguard
cluster nodes.
If temporary loss of failover protection is not tolerable, disable online migration for the VM. For
example, to disable the VM named sgnode, run the hpvmmodify command on the VSP as follows:
hpvmmodify -P sgnode -x online_migration=disabled
Do not attempt online migration of a VM configured as a Serviceguard cluster node. If a
Serviceguard node is migrated while online, it might lose connection to other cluster members and
be automatically removed from the cluster. Disable online migration for all VMs configured as
Serviceguard cluster nodes.
NOTE: Integrity Virtual Server Manager detects whether a VM is configured as a Serviceguard
package; the VSP Virtual Servers and VM Properties General tab tabs display the package icon
( ) next to the VM name.
For more information about managing VMs with Serviceguard support, see the HP-UX vPars and
Integrity VM Administrator Guide manual.
Capacity Advisor requirements and recommendations
If Capacity Advisor is used on the VM, collect utilization information before you migrate the VM.
The Capacity Advisor cannot continue to collect utilization information for the VM during the
migration.
Migration status and error notification
The migration status of a VM — including the direction of migration, percentage completion per
phase (for online migration only), and error messages — is displayed on the VM Properties General
tab. The VSP Virtual Servers tab also indicates migration status (use this tab to monitor the migration
of multiple VMs). For more information, see “VM or vPar properties general tab” (page 61) and
“VSP Virtual Servers tab” (page 31).
If errors occur during an attempt to migrate a VM online, the VSP Virtual Servers tab (for the source
VSP) displays the Migration Error icon ( ) next to the name of the affected VM. Information about
the migration-related errors is on the VM Properties General tab. For more information about status
icons, see “Status indicators” (page 141).
Various conditions can cause an online migration to abort: insufficient resources on the target host,
busy source or target hosts, a slow private network connection, an excessively busy guest (VM
operating system and applications), and so on. When a migration aborts, the guest continues to
run, unaffected, on the source VSP. Therefore, these are not serious errors. You can attempt the
online migration again when the blocking conditions improve.
After a VM successfully migrates to another VSP, it is placed in the Not Runnable state on the
source VSP. A VM in this state cannot be modified or started. If you never intend to migrate the
VM back to the source VSP, you can remove the VM configuration by using the Integrity Virtual
Server Manager Delete→Virtual Machine... menu item.
The state of the VM is displayed by the HW column on the VSP Virtual Servers tab. The Not
Runnable state is indicated by the following status icon: . The VM Properties General tab also
displays the state of the VM (in the Virtual Hardware Status field).
Working with VMs 99