HP-UX vPars and Integrity VM V6.3 Administrator Guide

nl
CAUTION: If the Virtual DVD drive of the guest is backed by a CD or DVD-ROM in the VSP that
is either an enclosure DVD-ROM or is assigned via vMedia, then the following exceptions apply:
• A vPar or VM guest configured with a virtual DVD that is backed by such a CD or DVD device
in the VSP fails to start up if the device is disconnected when the vPar or VM is being started.
• For such CD or DVD-ROMs, a media eject operation works like a drive disconnect, and hence,
the media eject operation succeeds irrespective of its usage by the VSP or by any of the active
vPars or VM guests.
Such devices can be identified by looking for “Virtual CD-ROM” or “Virtual DVD-ROM” in the
device description provided by the ioscan command.
For example, the ioscan output for an enclosure DVD-ROM:
#ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 4 255/1/0.0.0 sdisk CLAIMED DEVICE HP Virtual DVD-ROM
/dev/dsk/c21t0d0 /dev/rdsk/c21t0d0
Most physical VSP CD or DVD devices on HP Integrity servers have only one path to them, as
multipath software is not available on the VSP for them.
6.4.2.3.5 Virtual FileDVDs
A Virtual FileDVD is an emulated SCSI DVD, which uses a VSP ISO file as virtual media. The VSP
ISO file is specified using the absolute pathname to the ISO file. The file has to be on a VxFS file
systems locally mounted on the VSP. NFS file systems are not supported for Virtual FileDVDs.
Following is the Virtual FileDVD resource statement form:
dvd:avio_stor::file:/pathname/file.ISO
where /pathname/file.ISO specifies the VSP ISO file to use as virtual media.
You can create a VSP ISO file using the mkisofs utility or by using the dd command to copy CD
or DVD media to a file. The VxFS file system should be enabled to support largefiles, because
ISO files tend to be over 2 GB in size. All the ISO files that are useful to a guest OS should be
placed in the same directory to take advantage of dynamic changes using the virtual console (see
Section 6.5.2.3 (page 96)). The ISO files must be marked with proper permissions; they must not
be world writable. For example,
# ls -l /var/opt/hpvm/ISO-images/hpux
total 26409104
-rw-r--r-- 1 root sys 3774611456 Jul 11 :59 0505-FOE-OE.iso
-rw-r--r-- 1 root sys 4285267968 Jul 11 17:05 0512-FOE.iso
-rw-r--r-- 1 root sys 3149987840 Jul 11 18:42 0603-FOE-D1.iso
-rw-r--r-- 1 root sys 29978624 Jul 11 18:51 0603-FOE-D2.iso
In this example, the Virtual FileDVD resource statement form is:
dvd:avio_stor::file:/var/opt/hpvm/ISOimages/hpux/0603-FOE-D1.iso.
Virtual FileDVDs, such as all files, can take advantage of the multipath options with which the file
system is created. For more information, see Section 6.4.1.3 (page 69).
Virtual FileDVDs are read-only and are shareable across active VMs. You can use the hpvmdevmgmt
command to mark them as sharable.
To prevent media conflicts, you must manage Virtual FileDVDs (see Section 6.4.1.4 (page 69)).
You can know the location of the file system directory where the ISO file resides using the virtual
console of the guest. To simplify accounting, you can allocate file directories from complete logical
volumes or whole disks.
6.4 Configuring vPar and VM guest storage 83