HP-UX vPars and Integrity VM V6.3 Administrator Guide

• device is one of the following:
disk, dvd, tape, changer, burner, or hba
• pcibus is an integer from 0-7.
It represents the PCI bus number for the virtual device.
• pcislot is an integer from 0-7.
pcislot also referred to as the pcidevice, represents the PCI slot number for the virtual
device. A PCI function number is not specified. It is implicitly zero because the virtual storage
adapter supports only a single channel.
• target is an integer from 0–127 for AVIO. This is applicable only for non-NPIV backing
stores. All supported non-NPIV storage device types can share the same virtual AVIO adapter
by specifying the same PCI bus and slot numbers.
All targets connected to a vPar and VM guest are single LUN devices. That is, all virtual devices
are emulated as single LUNs. All virtual LUN numbers are implicitly zero and therefore not
specified.
A virtual adapter can only be added to a vPar or VM guest if it has a device connected to it, with
the exception of NPIV HBAs, where you can add a NPIV HBA to a vPar or VM guest without
presenting LUNs to it.
Not all device types are virtualized. Disk and DVD devices are virtual device types, whose virtual
media comes from the VSP. Tapes, changers, and burners are physical VSP devices. For these
attached devices, the physical IDs do not determine their place on the virtual bus.
NOTE: Certain PCI slots are used by vPars and VM guests for special devices. You can use the
hpvmstatus –P <guest_name> -V command to get a list of reserved slots. For more information
about dynamic addition of IO devices to vPars and VM guests, see Section 13.17 (page 247).
6.4.2.2 VSP storage specification
Each vPar and VM guest storage device is backed by some VSP storage entity. A VSP entity is
defined on the VSP with a system file, which is used by vPars and Integrity VM and the VSP
operating system in processing I/O to and from that storage entity.
A VSP administrator specifies these storage entities using the following specification:
storage:location
where:
• storage is one of the following:
disk, lv, file, null, attach_path, or npiv.
The selection of storage type defines what VSP system files apply. For example, lv implies
the use of logical volume character device files.
For virtual devices, the selection of VSP 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.
A VSP storage entity can only be used for one VM device type at a time. For example, a VSP
CD or DVD drive cannot be used for a Virtual DVD and an attached burner at the same time.
• location is a VSP system file.
The file permissions on the VSP system file or HW path for attach_path devices are not honored
by vPars and Integrity VM. vPar and VM guest device types that support write operations can
still do so using a VSP system file marked read only. Backing stores provided as virtual disks
can be written to regardless of the file permission settings on the backing store. A backing
76 Storage devices