HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

logical volumes or whole disks to make the accounting even easier. For more information, see
Section 6.2.1.4 (page 99).
The Virtual FileDisk resource statement takes the following form:
disk:scsi::file:/pathname/file
where the /pathname/file specifies the VM Host 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 VM Host 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:scsi::file:/fdev/frackA/disk1.
Multipath options for a Virtual FileDisk device are discussed in Section 6.2.1.3 (page 98).
NOTE: Each Integrity VM guest can support a maximum of 30 Virtual FileDisks (combined
limit for both AVIO and VIO).
6.2.2.3.4 Virtual DVDs
A Virtual DVD is an emulated SCSI DVD-ROM with virtual media that comes from a disc inside
of a CD/DVD drive on the VM Host. The VM Host 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 VM Host CD/DVD drives
prohibits them from being shared across active virtual machines. Thus only one active virtual
machine at time should be given a particular Virtual DVD resource. Virtual DVD resources can
be changed dynamically between active virtual machines (see Section 6.3 (page 113)).
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 virtual machine, make sure you know which virtual machine currently owns the device
before you load a CD/DVD. This information can be found on the VM Host with the hpvmstatus
commands.
The agile Virtual DVD resource statement takes the following form:
dvd:scsi::disk:/dev/rdisk/disk#
where /dev/rdisk/disk# is an HP-UX esdisk character device file for a VM Host CD/DVD
drive. The legacy Virtual DVD resource statement takes the form
dvd:scsi::disk:/dev/rdsk/cXtYdZ, where /dev/rdsk/cXtYdZ is an HP-UX sdisk
character device file for a VM Host CD/DVD drive.
Typically, the HP-UX esdisk and sdisk character files will already be created before booting
the VM Host. 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/rdsk/disk7
SCSI describe of /dev/rdsk/disk7:
6.2 Configuring Integrity VM Storage 107