HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

Because tapes, media changers, and CD/DVD burners are not virtualized, media changes with
them must be done physically. Therefore, all media changes with attached devices must be done
by individuals with access to that physical storage. Changes to attached devices might require the
device to be unlocked from an active guest OS. Attached devices remain in the last lock state the
guest OS put it in when the device is detached or the virtual machine is shut down. Empty devices
are attached and are not locked.
No multipath solutions are available for attached devices on the VSP. No multipath products are
supported in the vPar/VM.
Manage attached devices to prevent the wrong vPars/VMs from viewing sensitive information.
You can display which vPars/VMs are currently using attached devices using the hpvmstatus
command.
9.2.2.4 NFS-Mounted backing stores for root, swap, and dump
vPars and Integrity VM V6.1 supports NFS-mounted backing stores for root, swap and dump. These
backing-store files can now be located in NFS-mounted file systems. The following configuration
requirements apply. These configuration requirements might be removed or changed in future vPars
and Integrity VM releases.
• NFS-mounted backing stores can be used only for the root (that is, boot) file system, swap
and dump. NFS-mounted cannot be used as file-backed virtual DVD drives.
• The maximum number of NFS-mounted backing stores per guest is four.
• NFS-mounted backing stores are supported only for HP-UX 11i v3 guests.
• NFS-mounted backing stores must be configured with AVIO.
• The following NFS mount options must be used by the VSP when mounting an NFS file system
housing a guest's backing-store files:
◦ NFS Version 3
◦ TCP
◦ Hard
◦ IPv4 address or server host names mapping to IPv4 address
• The Integrity VSP (NFS client) and the NFS server systems must reside in the same IP subnet.
• Online VM Migration is supported for VMs using NFS-mounted backing stores. For OVMM
to work successfully, both Integrity VSPs must mount the NFS file system housing the guest's
backing-store files using the identical syntax and mount options. Both the source and target
VSPs must have the NFS file system mounted at the time of the migration.
The following limitations apply to this release of the NFS-mounted backing stores feature in vPars
and Integrity VM V6.1:
• Integrity VM guests configured with NFS-mounted backing stores cannot be integrated with
Serviceguard as either a package (VM-as-an-SG-Package) or node (VM-as-an-SG-Node).
• The use of symbolic links on the NFS server to redirect the location of a guest's backing-store
files is not allowed. However, symbolic links are still allowed inside the guest booted with an
NFS backing store.
• NFS file systems housing a guest's backing stores must be mounted using IPv4. Mounting NFS
backing stores using IPv6 is not allowed at this time.
• Management of Integrity VM guests configured with NFS-mounted backing stores is not
supported with the following management applications:
132 Creating virtual storage devices