HP-UX vPars and Integrity VM V6.1.5 Administrator Guide (5900-2295, April 2013)

Multipath products not using NPIV for storage resources must run on the VSP; multipath solutions
without NPIV devices are not supported in a vPar/VM.With NPIV devices, the multipathing products
can run on the vPar or VM guest itself. All multipath solutions used on the VSP must be in valid
supported configurations before being used for vPar/VM storage resources (see Section 9.2.1.3
(page 120)).
The resource statements in the following subsections do not contain vPar/VM hardware addressing.
The PCI bus, PCI slot, and AVIO target numbers are optional.
9.2.2.3.1 Virtual Disks
A Virtual Disk is an emulated AVIO disk whose virtual media comes from a VSP disk LUN. The
VSP disk LUN is specified using a character device file. The character device file is owned by the
HP-UX esdisk driver.
Virtual Disk resources cannot be shared simultaneously across active vPars/VMs (except in certain
cluster configurations, as indicated in this manual). Only one active vPar/VM at time can be given
a particular Virtual Disk resource. Virtual Disk resources can be changed dynamically among active
vPars/VMs.
To prevent virtual media conflicts that can result in data corruption, a proper accounting of how
the VSP whole disks are allocated for use by Virtual Disks needs to be done, as described in
Section 9.2.1.4 (page 121).
The Virtual Disk resource statement takes the form:
disk:avio_stor::disk:/dev/rdisk/diskX
where /dev/rdisk/diskX is an HP-UX esdisk character device file.
These device files can be located for a VSP LUN using the ioscan command. These system files
are installed and removed using the insf and rmsf commands, respectively. Device files are
created automatically by the VSP for any storage it identifies during boot. New devices connected
or created after boot time, require the use of ioscan and insf to create the new device files. To
remove old device files for storage that is no longer present, use the rmsf command. For example:
# ioscan
# ioscan -NfunC disk
disk 64000/0xfa00/0x10 esdisk CLAIMED DEVICE
HP HSV210
/dev/disk/disk /dev/rdisk/disk
9.2.2.3.2 Virtual LvDisks
A Virtual LvDisk is an emulated AVIO disk whose virtual media is provided by a raw VSP logical
volume. To specify a VSP logical volume, use a character device file. The character device file is
owned by either LVM or VxVM.
Virtual LvDisks cannot be shared simultaneously across active vPars/VMs. Only one active vPar/VM
at time can be given a particular Virtual LvDisk resource. Virtual LvDisk resources can be changed
dynamically between active vPars/VMs (see Section 9.3 (page 135)).
Logical volumes can be created using the sam utility or the Veritas Enterprise Administrator.
Alternatively, logical volumes can be created using the commands available with the volume
manager. All logical volumes are created on whole disks. The sizes of the logical volumes come
from the space available from their respective volume group types; that logical volume size can
be increased without loss of data in the volume. The character devices for the logical volumes are
created by their respective volume managers at the time the logical volume is created. Also to
avoid file system corruptions for the VSP and guest , use only raw logical volumes that contain no
VSP file systems and are not currently mounted on the VSP.
To prevent data corruptions, keep an account of logical volumes for Virtual LvDisks. To help with
the accounting, use all logical volumes within a given volume group for a single virtual machine.
126 Creating virtual storage devices