AVIO is supported by multiple
guest operating systems and is optional based on a properly configured
VM Host and changes to the guest operating systems. For AVIO support
details, see the HP Integrity Virtual Machines Version
4.1 Release Notes and the AVIO product documentation.
You must install and configure kernel drivers on both the VM Host
and the guest systems. The guest configuration file and the hpvmstatus command display the avio_lan and avio_stor designators.
 |
 |  |
 |
 | NOTE: HP strongly recommends that you use the same AVIO components
from the same release on both the VM Host and guests, for example,
both from the OE or both from the same Web Release (for example, WEB0803). |
 |
 |  |
 |
The following example shows the hpvmstatus command output of AVIO adapters for guest avioclone:
[Storage Interface Details]
Guest Device type :disk
Guest Adaptor type :avio_stor
Bus :0
Device :0
Function :0
Target :3
Lun :0
Physical Storage type :disk
Physical device :/dev/rdisk/disk2
[Network Interface Details]
Physical Storage type :vswitch
Guest Adaptor type :avio_lan
Backing :swlan1
Vswitch Port :5
Bus :0
Device :1
Function :0
Mac Address :2a-2e-5a-05-0a-ba
Physical Storage type :vswitch
Guest Adaptor type :avio_lan
Backing :swlan2
Vswitch port :9
Bus :0
Device :2
Function :0
Mac Address :2a-2e-5a-05-0a-bc |
 |
 |  |
 |
 | NOTE: The CLI accepts either avio_lan or aviolan and either avio_stor or aviostor. For example, the following hpvmcreate commands add both an AVIO network and an AVIO
disk to the guest aviotest:# hpvmcreate -P aviotest -O hpux -a network:aviolan::vswitch:swlan1 \
-a hba:aviostor::disk/dev/rdisk/disk1
# hpvmcreate -P aviotest -O hpux -a network:avio_lan::vswitch:swlan1 \
-a hba:avio_stor::disk/dev/rdisk/disk1 |
|
 |
 |  |
 |
The AVIO network host driver allows simultaneous
access to a vswitch from guests configured with or without AVIO guest
drivers for their virtual network interface cards (vNICs). Existing
guests continue to operate correctly and their configurations remain
unchanged. Guests configured to use a common vswitch are allowed to
share VLANs that are in use by guests with or without AVIO configured.
Ports remain distinct for each running guest whether or not AVIO is
in use. AVIO networks must use a Supported Host Physical Point Attachment
(PPA) network device. For a list of supported AVIO PPAs, see the HP Integrity Virtual Machines Version 4.1 Release Notes. A nonphysical vswitch, such as localnet, is not supported in this
release.
AVIO increases the maximum
number of devices that can be supported in a guest to 128. In this
release, AVIO supports the disk and DVD device types, while burner,
tape, and changer device types are not supported. The dynamic addition
and deletion of AVIO devices is supported. The following backing-store
options are supported:
Disk (such as /dev/rdisk/disk1)
Null (for DVD devices only)
All other backing store options, such as null
for non-DVD devices and attached, are not supported.
 |
 |  |
 |
 | NOTE: In general, AVIO devices (that is, avio_lan, aviolan, avio_stor, or aviostor) are configured and managed the same as VIO devices
(that is lan and scsi). However,
some additional Integrity VM command options and limitations on backing
devices are noted throughout this document. |
 |
 |  |
 |
With HP-UX 11i v3, the AVIO storage guest driver
can receive events asynchronously from the VM Host for avio_stor devices whenever the underlying storage, such as lun or target,
changes state, for example, when a new lun or target is added or deleted
or when the size of a lun changes. The asynchronous event generation
occurs in addition to any notifications issued using the SCSI programming
model, such as CHECK CONDITION on a subsequent I/O.
When the AVIO storage driver on the guest detects
the events, it takes the appropriate actions, such as discovering
the new targets. For example, if new targets are added using the hpvmmodify -a command, then the guest
driver automatically detects the new device without the manual scan.
The guest automatically detects any modification of the underlying
backing storage.