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

Changing the policy to enumerate all AVIO storage devices might result in longer guest boot times
(to the EFI level), depending on the guest's configuration.
If you need to boot from a tape device attached to an NPIV (such as performing tape-based Ignite-UX
recovery), change the enumeration policy to "Enumerate all FC LUNs". As mentioned previously,
enumerating all FC LUNs can result in a long guest boot time. To minimize this delay, you can
temporarily reduce the number of NPIV HBAs for the VM to only the one containing the tape boot
device.
8.2.2 VM Guest Running on an NFS Backing Store
The information in the HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration
is incomplete. This section provides the necessary information needed to create a VM Guest on
an NFS backing store. From an Integrity VM perspective, an NFS backing store is a file-based
backing store. That is, the Integrity VM boot image is contained in single file residing in the NFS
mounted directory. From an NFS perspective, the VM Host is the NFS client, so that it mounts the
shared directory where the VM guest boot disk will be stored from the NFS server.
For example, NFS server nfs-serv is sharing a directory called /nfs-hpvm that houses the
VM guest boot image file. In this example, the VM Host mounts this shared directory using NFS.
The location where the directory is mounted is /vm-guest1. The resulting NFS mount syntax i:
vmhost# mkdir /vm-guest1
vmhost# mount nfs-serv:/nfs-hpvm /vm-guest1
Once the VM Host has the NFS directory mounted, you can create the VM Guest backing store
file in the mounted directory using the hpvmdevmgmt(1M) command:
vmhost# cd /vm-guest1
vnhost# hpvmdevmgmt -S 40G bootfile
Once the backing store file is created, it can be added to the VM Guest configuration with either
the hpvmcreate command or the hpvmmodify command. The resulting guest would look like:
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk avio_stor 0 0 0 0 0 file /vm-guest1/bootfile
At this point you should be able to boot the VM Guest and install the operating system as you
would any other VM Guest.
8.2.3 Storage Interface Support for OpenVMS Guests
The OpenVMS guest supports the AVIO interface, however, Integrity VM commands allow you to
configure both AVIO and VIO devices to a guest. These VIO devices might not give any apparent
errors during the startup. VIO devices and attached AVIO devices are not supported on OpenVMS
guests.
8.2.4 Recommended Host AVIO and Guest AVIO Storage and Network Versions
The following table shows the recommended Host AVIO and Guest AVIO storage versions:
8.2 Changes and Issues in This Release 37