|HP Integrity Virtual Machines Version 4.0 Release Notes > Chapter 8 Storage Information
The following sections describe the current limitations using AVIO.
If you attempt to modify a storage adapter from scsi to avio_stor on a port for a running guest, the hpvmmodify command allows the change, but the change lasts only until the next guest startup. In addition, the hpvmnet command displays incorrect port information for the currently running guest until the guest is stopped and restarted.
A dvd drive configured under AVIO as null physical storage prints error messages indicating read capacity failure during guest startup. For example, if you configure a DVD as follows, you receive the subsequent messages:
The following boot up error messages are seen:
When using USB DVD drives, these error messages are harmless and may be ignored.
A DVD drive that is not USB, configured under AVIO as null physical storage, fails with an I/O error when a guest console INsert operation is attempted. For example, if you configure the DVD as follows, you receive the subsequent messages:
The following messages appear when the guest console INsert operation fails:
To work around the issue, configure the DVD as disk instead of null or configure the DVD under scsi adapter instead of avio_stor.
AVIO does not yet support tapes, changers, or burners. VxVM logical volumes are not supported.
If the GuestAVIOStor bundle is not installed on the HP-UX guest, any configured AVIO Stor HBAs will not be claimed in the guest, and the LUNs configured under the AVIO Stor HBAs will not be accessible. If the LUN is a boot disk, boot will fail with a panic indicating missing drivers.
The agile DSFs in an HP-UX 11i v3 guest change either when an entire HBA or an individual disk is migrated between SCSI and AVIO.
When an entire HPA is migrated between SCSI and AVIO for an HP-UX 11i v3 guest, new agile DSFs are created for the migrated disks instead of reusing the old agile DSFs. This is because the design for agility is different in HP-UX 11i v3 between parallel SCSI and other HBAs (for example, FC, AVIO). A new agile DSF is also created instead of reusing the old agile DSF when an individual disk is moved between SCSI and AVIO HBAs.
Prior to migrating an individual disk or an HBA between SCSI and AVIO for an HP-UX 11i v3 guest, run ioscan and ioscan —m dsf on the guest to get an inventory of the disks. The corresponding agile DSFs remain the same, so that the old and new agile DSFs can be obtained corresponding to the legacy DSFs. For migration of individual disks, the old and new legacy DSFs can be used to locate the corresponding agile DSFs.
If a backing store is not responsive due to device errors, it might take up to 30 seconds on an HP-UX 11i v2 guest to report a failure. For example, the diskinfo command might fail after 30 seconds:
This delay is caused by the retry of failed commands from the nonresponding backing store. There is currently no workaround.
Devices configured under AVIO Stor HBA for a guest cannot be deleted (using the hpvmmodify command) if the guest is at EFI.
Stop the guest using the hpvmstop command and retry the command.
The hpvmmodify command on an AVIO device on an HP-UX 11i v3 guest might fail with device busy error if the guest is online and has opened the device. In this case, the device must be removed from the 11i v3 guest using rmsf for the lun path or target path before executing the hpvmmodify command,
This section explains how to map an AVIO storage device on an HP-UX guest to an hpvmstatus display on the Integrity VM Host either at the EFI console or at the HP-UX operating system.
The following example shows the output of hpvmstatus from the Integrity VM Host:
The following statistics are displayed in this example:
Note that Addr (Target Id) is decimal in the hpvmstatus display, and PciFtn and Lun are always zero (0).
The Integrity VM guest EFI device path encodes PciBus, PciDev, and Addr (Target Id) from the hpvmstatus display:
PciFtn (PCI function) and Lun# are always zero (0). Addr (Target Id) becomes EFI Pun# and is displayed as a hexidecimal number.
The two methods for mapping an Integrity VM HP-UX guest hardware path or HP-UX Device Specific File (DSF) to an Integrity VM Host hpvmstatus display: