HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

To check if a guest can be migrated to the target VSP, use the hpvmmigrate -s option.
12.1.2 Reasons for migrating virtual machines or vPars offline
This sections lists reasons why you might want to migrate a virtual machine or vPar offline. For
example:
• The vPar or VM might be stopped, so you need to move the configuration information offline.
• Migrating the virtual machine or vPar offline does not use the VSP resources (like memory and
CPUs) on the source and target VSPs. (You can migrate vPars offline only.)
• The vPar or VM might have local storage, logical volumes or file-backed storage, which must
be copied to the target VSP.
• The source and target VSPs might have different processor types that prevent online migration.
• The source VSP might be running a version of Integrity VM prior to Version 6.1, which does
not support Online VM Migration.
• You can offline migrate vPars or VMs between different processor families.
Table 32 provides the migration path for offline migration:
Table 32 Offline Migration Paths
Supported Offline Migration Path (Forward or Backward)vPars and Integrity VM Version
Integrity VM V3.5Integrity VM V3.5
Integrity VMV4.0Integrity VM V4.0
Integrity VM V4.1 or laterIntegrity VM V4.1 or later
vPars V6.1vPars V6.0
Offline migration of a vPar or VM with DIO functions assigned to it requires that each function is
assigned a label using the hpvmhwmgmt -L label switch. (See hpvmhwmgmt(1M) for the
command syntax.) Additionally, there must be at least one DIO-capable function with the same
label on the target VSP for each DIO-capable function on the vPar or VM on the source VSP.
A label may contain up to 256 alphanumeric characters, including A-Z, a-z, 0-9, the dash (-), the
underscore (_), and the period (.), except that it may not be the string "." or "..". Labels only apply
to DIO functions that have been added to the DIO pool on the source and target VSPs with:
hpvmhwmgmt -p dio -a hwpath
If any DIO function in a vPar or VM has no label, offline migration will fail. There may be more
functions with the same label available on the target VSP than are needed to do a one-to-one
matching of DIO-functions on the target VSP, but there must be at least a one-to-one correspondence
between each labeled function on the source vPar or VM and available DIO-capable functions on
the target VSP.
HP recommends that labels be assigned to correspond to IP names, so that the network mapping
on the source vPar or VM is preserved when the vPar/VM is migrated to the target VSP. That is
not a requirement for offline migration to succeed, but failure to maintain the one-to-one
correspondence with IP names might cause problems when the migrated vPar or VM is started.
Label-matching is independent of whether the labels are assigned to DLA or FLA functions. See
“Using direct I/O networking” (page 19) for an explanation of DLA and FLA distinction. However,
offline migration will attempt to do an exact match of like-for- like function types first.
12.2 Command line interface for online and offline migration
To migrate a virtual machine to another VSP, perform the following steps:
198 Migrating virtual machines and vPars