How to migrate HP-UX workloads between physical and virtual servers easily

Figure 4. Portable image execution during shutdown and boot phases

Note: You can also use the HPPortableImage product to retain PPAs when performing a vPar/VM type transformation in an HP Integrity

VM/vPar 6.x environment. Before changing the virtual server type (vm_type), issue kctune gio_portable_image=1 in the virtual server

and shut it down gently. For more information on vPar/VM virtual server types, consult the HP-UX vPars and Integrity VM 6.1 administrator guide at

hp.com/go/hpux-hpvm-docs.

vmVirtProvider

The WBEM vmVirtProvider product is an interface between HP Integrity VM hosts and the Virtual Machine Manager

(VMM). Among other things, it is responsible for executing requests coming from the VMM (i.e., virtual machine creation)

and for sending back various status and configuration information. In HP Integrity VM 4.x, it is a product part of the

T2767CC bundle. In HP Integrity VM 6.x, it is part of the BB068AA bundle.

You can use the following command to list the status of vmVirtProvider and verify it is operating correctly:

/opt/wbem/bin/cimprovider -l -s | grep -i virtp

VirtProviderModule OK

N-Port ID Virtualization (NPIV) support

Traditionally, in virtualized infrastructures, hypervisors present SAN disks as SCSI devices to virtual machines and

perform a protocol translation (SCSI/FC), so virtual machines can communicate seamlessly with their SAN storage.

In this context, virtual logical servers characterize their storage with SCSI IDs as storage attributes. In a physical

environment, logical servers need World Wide Name (WWN) identifiers, in addition to SCSI IDs to be able to access the

SAN storage using the Fiber Channel protocol. Having different attributes for storage characterization in virtual and

physical environments adds complexity to unlike moves.