HP Integrity Virtual Machines 4.3: Release Notes (5900-2265, May 2012)

9 Migrating Virtual Machines
This chapter contains information about migrating virtual machines.
9.1 Changes included in V4.3 May 2012 Patch Release
The following section provides information about the V4.3 May 2012 Patch Release.
9.1.1 Issue with V4.2.5 VM Suspended then Migrated to V4.3 VM Host
A VM running on a V4.2.5 system with the V4.2.5 HPVM-Guest kit installed and then suspended
and online or offline migrated to a V4.3 VM Host, fails to resume on a V4.3 VM Host.
Workaround: Before performing an online or offline migration or upgrading to a V4.3 VM Host,
install the V4.3 HPVM-Guest kit in the VM guest on the V4.2.5 VM Host.
9.2 Change included in V4.3 January 2012 Patch Release
The following section provides information about the V4.3 January 2012 patch release.
9.2.1 Migrating VMs with NPIV Devices
Starting with the 4.3 January 2012 patch release, Integrity Virtual Machine (Integrity VM) supports
migration of VMs that include NPIV AVIO devices. This includes both online and offline migration.
The requirements for migrating a VM are still the same. All resources used by the VM must be
configured symmetrically on both the source and target host.
If the VM includes NPIV devices, the target Host must choose a physical Fibre Channel HBA (PFC)
on which to create the NPIV device, such as /dev/fcd0. One important requirement is that after
migration, the VM's NPIV device must see the same Fibre Channel (FC) target paths as before the
migration.
The FC targets that an NPIV device sees depends on the zoning settings of the FC switch. Therefore,
hpvmmigrate will choose the target host PFC based on the following:
• The PFC on the target Host must support NPIV.
• The PFC must have available Integrity VM NPIV entries.
• The FC switch must use World-Wide-Name (WWN) based zoning, as opposed to Port zoning.
Each PFC has a maximum number of NPIV entries (like 8 or 16), and some of these entries might
be active (in use). The “available NPIV entries” is the maximum supported NPIV entries minus the
active NPIV's. In the following example, the available NPIV entries is 2:
# /opt/fcms/bin/fcmsutil /dev/fcd1 npiv_info
HPVM Virtual Fibre Channel (VFC)
----------------------------------
Maximum Supported HPVM VFC = 8
Number Active HPVM VFC = 6
If both the source and target are connected to the same FC switch, and the FC switch uses
World-Wide-Name (WWN) based zoning, then the NPIV is guaranteed to see the same FC targets
as before. This is because the NPIV's virtual Port WWN is still the same after migration.
To see which FC switch a PFC is connected to, use the fcmsutil command and look for the
Switch Node World Wide Name value:
# /opt/fcms/bin/fcmsutil /dev/fcd0
Switch Port World Wide Name = 0x200800051e0351f4
Switch Node World Wide Name = 0x100000051e0351f4
9.1 Changes included in V4.3 May 2012 Patch Release 41