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

Figure 18. Virtual logical server activation

Note: The different steps of logical server activation on a HP Integrity VM host can be viewed on the host with the command:

tail -f /var/opt/hpvm/common/command.log

The activated logical server appears in green from the Logical Server perspective of the HP Matrix OE

visualization as shown in figure 19. The status is grayed and the utilization bars don’t mention any activity,

since there is no operating system running yet in the virtual machine.

Figure 19. Activated logical server

Deploying and configuring HP-UX in the logical server

At the end of the activation process, a power-on operation is performed as requested in the target selection screen

(shown at the bottom of figure 16). This brings the logical server at the EFI level. Before deploying an HP-UX OE,

we may need to configure the HP AVIO Stor EFI driver to enumerate all Fiber Channel SAN devices. By default and to save

initialization times only SCSI and FC LUNs matching an EFI boot entry are listed by the map command. Since this is the

first time we boot this virtual machine, no boot entry is present and as a result no device is visible from the EFI shell.

To make FC LUNs visible, connect to the HP Integrity VM console and, at the EFI prompt, type drvcfg -s and answer Y

to the Enumerate all FC LUNs (Y/N):? question (Figure 20), and then reset the virtual machine.