The following sections describe the current limitations using
AVIO.
Modifying the Storage Adapter from scsi to avio_stor |
 |
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.
Guest Boot Error Messages on AVIO null DVD |
|
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:
(hpux) />hpvmstatus -P guest1 -d
[Virtual Machine Devices]
[Storage Interface Details]
dvd:avio_stor:7,7,127:null:/dev/rdisk/disk465 |
The following boot up error messages are seen:
VsdDetectMedia: VsdReadCapacity() failed. PCI bus/dev=0x7/0x7, VSD LUN
ID=0x7F.ReadCapacityStatus=0x8000000000000007.
VsdDetectMedia: VsdReadCapacity() failed. PCI bus/dev=0x7/0x7, VSD LUN
ID=0x7F.ReadCapacityStatus=0x8000000000000007. |
When using USB DVD drives, these error messages are harmless
and may be ignored.
Guest Console INsert Failure on AVIO null DVD |
|
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:
(hpux) /> hpvmstatus -P guest1 -d
[Virtual Machine Devices]
[Storage Interface Details]
dvd:avio_stor:7,7,127:null:/dev/rdisk/disk465 |
The following messages appear when the guest console INsert
operation fails:
[guest1] vMP> in
Insertable Guest Devices
Num Hw-path (Bus,Slot,Tgt) Gdev
--------------------------------------------
[1] 0/7/7/0.127.0 (7,7,127) dvd
Enter menu item or [Q] Quit: 1
Num File
--------------------
[1] /dev/rdisk/disk465
Enter menu item number or [Q] to Quit: 1
Confirm insertion action
G - GO
F - Force
Enter menu item or [Q] to Quit: g
** Error: operation failed with error: I/O error ** |
To work around the issue, configure the DVD as disk instead of null or configure the DVD under scsi adapter instead of avio_stor.
Virtual Device Types and Backing Store Support |
|
AVIO does not yet support tapes, changers, or burners. VxVM
logical volumes are not supported.
GuestAVIOStor Bundle not Installed but AVIO Storage Device
is Configured |
|
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.
Agile DSFs Change in HP-UX 11i v3 Guest When Migrating Disks
Between scsi and avio_stor |
|
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.
Longer Failure Reporting Time for AVIO Devices on 11i v2 Guests |
|
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:
# time diskinfo /dev/rsdk/c1t14d0:
diskinfo: can't open /dev/rdsk/c1tl4d0: No such device or address
real 0m30.26s
user 0m0.00s
sys 0m0.01s |
This delay is caused by the retry of failed commands from the
nonresponding backing store. There is currently no workaround.
Online Modification of AVIO Devices Might Fail |
|
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,
Mapping AVIO Storage Devices on 11i v2 Guests |
|
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:
# hpvmstatus -P aviotest
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk avio_stor 0 2 0 22 0 disk /dev/rdsk/c82t15d3 |
The following statistics are displayed in this example:
Addr (Target Id) = 22 (0x16)
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:
PciDev
|
| PCIFtn
PciBus | | Addr(Target Id)
| | | |
V V V V
blk16 : Acpi(PNP0A03,0)/Pci(2|0)/Scsi(Pun16,Lun0) |
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:
-e option of the ioscan utility
ioscan -fne displays the HP-UX hardware path/DSF and the EFI device path for
the device. The HP-UX hardware path encodes the following from the hpvmstatus display:
Addr (Target Id) is encoded as an HP-UX tgt ID and an HP-UX
lun ID in the HP-UX hardware path.
HP-UX tgt ID and HP-UX lun ID are calculated from Addr (Target
Id) in the hpvmstatus display using the following
equations:
HP-UX tgt ID = Addr(Target Id) % 16
HP-UX lun ID = Addr(Target Id) / 16
|
Note the following example:
# ioscan -fne
PciDev
| PCIFtn
| |(Addr(Target Id) % 16) <-> HP-UX tgt ID
PciBus | | |(Addr(Target Id) / 16) <-> HP-UX lun ID
| | | | |
V V V V V
disk 49 0/0/2/0.6.1 sdisk CLAIMED DEVICE HP Virtual Disk
/dev/dsk/c0t6d1 /dev/rdsk/c0t6d1
Acpi(PNP0A03,0)/Pci(2|0)/Scsi(Pun16,Lun0)
^ ^ ^ ^
| | | |
PciBus | PCIFtn Addr(Target Id)
|
PciDev
|
In this example, exp1 / exp2 represents the quotient from exp1
divided by exp2 (integer division), and exp1 % exp2 finds modulo of
exp1 divided by exp2 (that is, finds the remainder of an integer division).
get_info option of the gvsdmgr utility
If you are using the HP-UX DSF, the following gvsdmgr option can be used to get the VSD LUN ID, which
is the same as the Addr (Target Id) in the hpvmstatus display. The gvsdmgr utility displays VSD LUN
Id as a hexidecimal number. The first nibble of VSD LUN Id becomes
HP-UX lun ID, and the second nibble becomes HP-UX tgt ID. The following
example shows the get_info option with the gvdsmgr utility:
# gvsdmgr get_info -D /dev/gvsd0 -q lun=/dev/rdsk/c0t6d1
Tue Oct 2 13:35:32 2007
Lun DSF : /dev/rdsk/c0t6d1
VSD LUN Id : 0x16
Lun Hardware path : 0/0/2/0.6.1
LUN State : UNOPENED
|
Printable version
