HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

The Virtual FileDisk resource statement takes the following form:
disk:avio_stor::file:/pathname/file
where the /pathname/file specifies the VSP file used as virtual media.
A VxFS file system can be created on top of a whole disk or logical volume. For files over 2 GB,
VxFS requires the file system be marked with a largefiles option. The mkfs command can be
used to create the VxFS file systems directly. Once the file systems are created, mount can be
used to mount them onto the VSP file system. Alternatively, if using logical volumes to create the
file system on, the volume manager GUIs like sam can be used to create the file systems and their
mount points, when the logical volumes are created. In any case, once the file system is mounted,
you can create empty files for Virtual FileDisk using the hpvmdevmgmt command.
# mkfs -F vxfs -o largefiles /dev/disk/disk237
# mount /dev/disk/disk237 /fdev/frackA/
# hpvmdevmgmt -S 4G /fdev/frackA/disk1
In this example, the Virtual FileDisk resource statement is
disk:avio_stor::file:/fdev/frackA/disk1.
Multipath options for a Virtual FileDisk device are discussed in Section 9.2.1.3 (page 118).
NOTE: Each vPar/VM can support a maximum of 30 Virtual FileDisks.
9.2.2.3.4 Virtual DVDs
A Virtual DVD is an emulated AVIO DVD-ROM with virtual media that comes from a disc inside
of a CD/DVD drive on the VSP. The VSP CD/DVD drive is specified using an HP-UX sdisk character
device file.
While the Virtual DVD is read-only, the slowness of the physical VSP CD/DVD drives prohibits
them from being shared across active vPars/VMs. Thus only one active vPar/VM at time should
be given a particular Virtual DVD resource. Virtual DVD resources can be changed dynamically
between active vPars/VMs (see Section 9.3 (page 133)).
Because the Virtual DVDs are read only, they do not require management to prevent conflicts
writing to the device. However, to prevent sensitive information from being accessed by the wrong
vPar/VM, make sure you know which vPar/VM currently owns the device before you load a
CD/DVD. This information can be found on the VSP with the hpvmstatus commands.
The agile Virtual DVD resource statement takes the following form:
dvd:avio_stor::disk:/dev/rdisk/disk#
where /dev/rdisk/disk# is an HP-UX esdisk character device file for a VSP CD/DVD drive.
The legacy Virtual DVD resource statement takes the form
dvd:avio_stor::disk:/dev/rdisk/cXtYdZ, where /dev/rdisk/cXtYdZ is an HP-UX
sdisk character device file for a VSP CD/DVD drive.
Typically, the HP-UX esdisk and sdisk character files will already be created before booting
the VSP. If they are not, they can be created and managed using the ioscan, insf, and rmsf
utilities. For example:
# ioscan -NfunC disk
disk 7 64000/0xfa00/0x6 esdisk CLAIMED DEVICE
TEAC DW-224E
/dev/disk/disk7 /dev/rdisk/disk7
# diskinfo /dev/rdisk/disk7
SCSI describe of /dev/rdisk/disk7:
vendor: TEAC
product id: DW-224E
type: CD-ROM
size: 4300800 Kbytes
bytes per sector: 2048
9.2 Configuring vPar/VM storage 127