HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

pcislot is an integer from 0-7.
A PCI function number is not specified. It is implicitly zero because the virtual MPT storage
adapter supports only a single channel.
scsitgt is an integer from 0-14 for virtual SCSI (15 is reserved for the virtual SCSI adapter)
and 0–127 for AVIO. All supported storage device types can share the same virtual SCSI
MPT or AVIO adapter by specifying the same PCI bus and slot numbers. A virtual SCSI
MPT or AVIO adapter can be added only to a virtual machine if it has a device connected
to it.
Unlike real parallel SCSI bus, there is no arbitration on virtual SCSI buses. The SCSI target
IDs for the virtual devices must be unique.The virtual SCSI MPT adapter takes target ID 15
for itself, leaving 0-14 for SCSI targets.
All SCSI targets connected to a VM are single LUN devices. That is, virtual disks and DVDs
are emulated as single LUNs and all attached devices are specified by per LUN VM Host
system files. The physical LUN number of an attached device has no impact. All virtual and
attached SCSI LUN numbers are implicitly zero and therefore not specified.
All supported storage device types can share the same virtual SCSI MPT adapter. Up to 15
storage devices can be added to the same SCSI MPT adapter by specifying the same PCI bus
and slot numbers.
A virtual SCSI MPT adapter can be added only to a virtual machine if it has a device connected
to it.
Not all device types are virtualized. Disk and DVD devices are virtual device types, whose virtual
media comes from the VM Host. Tapes, changers, and burners are physical VM Host devices.
For these attached devices, the physical SCSI IDs do not determine their place on the virtual bus.
7.2.2.2 VM Host Storage Specification
Each VM storage device is backed by some VM Host storage entity. A VM Host entity is defined
on the VM Host with a system file, which is used by Integrity VM and the VM Host operating
system in processing I/O to and from that storage entity.
A VM Host administrator specifies these storage entities using the following specification:
storage:location
where:
storage is one of the following: disk, lv, file, null, or attach.
The selection of storage type defines what VM Host system files apply. For example, lv
implies the use of logical volume character device files.
For virtual devices, the selection of VM Host storage determines what type of virtual media
the virtual device uses. For example, the selection of lv for a virtual disk, makes it a Virtual
LvDisk to the VM. It does not support the attach storage type.
A VM Host storage entity can only be used for one VM device type at a time. For example,
a VM Host CD/DVD drive cannot be used for a Virtual DVD and an attached burner at the
same time.
location is a VM Host system file.
The file permissions on the VM Host system file are not honored by Integrity VM. VM device
types that support write operations can still do so using a VM Host system file marked read
only.
More than one VM Host system file might point to the same VM Host storage entity. For
example, if multiple paths to storage are present on the VM Host, more than one disk system
file can point to the same disk. Different VM Host system files change how I/O is routed to
the VM storage resource, but the system files point to the same storage entity. Therefore,
different system files cannot constitute different VM storage resources. A given VM storage
7.2 Configuring Integrity VM Storage 109