HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

These device files can be located for a VM Host 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 VM Host for any storage it sees during boot. New devices
connected or created after boot time, require the use of ioscan and insf to create the new
sdisk device files. Old device files for storage not longer present can be removed with rmsf.
For example:
# ioscan
# ioscan -funC disk
disk 110 0/5/1/0.11.16.0.0.0.2 sdisk CLAIMED DEVICE HP A6188A
disk 116 0/5/1/0.11.16.0.0.0.3 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c19t0d3 /dev/rdsk/c19t0d3
# insf -H 0/5/1/0.11.16.0.0.0.2
# ioscan -funC disk
disk 110 0/5/1/0.11.16.0.0.0.2 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c19t0d2 /dev/rdsk/c19t0d2
disk 116 0/5/1/0.11.16.0.0.0.3 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c19t0d3 /dev/rdsk/c19t0d3
In this example, the Virtual Disk Resource Statement is
disk:scsi::disk:/dev/rdsk/c19t0d2.
If you are using HP Securepath/Autopath for Virtual Disks, you can use either sdisk device
files or virtual device special files (VDSFs). Both device paths provide high availability for the
virtual machine and can be used interchangeably. For information about enabling these device
paths, see the HP Securepath/Autopath documentation.
If you are using EMC PowerPath for a Virtual Disk, make sure that the sdisk device files that
you use for Virtual Disks are enabled for use by the multipath product. Consult the multipath
vendor's documentation for more information.
7.2.2.3.2 Virtual LvDisks
A Virtual LvDisk is an emulated SCSI disk whose virtual media is provided by a raw VM Host
logical volume. To specify a VM Host 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 virtual machines. Only one active
virtual machine at time can be given a particular Virtual LvDisk resource. Virtual LvDisk resources
can be changed dynamically between active virtual machines (see Section 7.3 (page 102)).
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 VM Host and guest , use only raw logical volumes that
contain no VM Host file systems and are not currently mounted on the VM Host.
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. When logical volumes are configured this way, you only have to keep track of the
volume groups to prevent media conflicts. See Section 7.2.1.4 (page 88) for information about
tracking virtual media allocation.
If you are using LVM, the Virtual LvDisk resource statement takes the following form:
disk:scsi::lv:/dev/vg_name/rlvol_name
94 Creating Virtual Storage Devices