HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

disk:scsi:0,4,2:lv:/dev/vg01/rlvol2
disk:scsi:0,4,3:lv:/dev/vg01/rlvol3
disk:scsi:0,4,4:disk:/dev/rdisk/disk20
dvd:scsi:0,4,5:file:/fdev/0x500000e012afb8d2/file2
:
# hpvmmodify -P guest1 –d tape:scsi:0,4,0:attach:/dev/pt/pt_tape1
# hpvmmodify -P guest1 -m hba:avio_stor:0,4
# ioscan -m lun /dev/pt/pt_tape1
Class I Lun H/W Path Driver S/W State H/W Type Health Description
======================================================================
tape 1 64000/0xfa00/0x0 estape CLAIMED DEVICE online STK T9940B
0/1/1/1.0x500104f00048b29d.0x0
0/7/1/1.0x500104f00048b29e.0x0
/dev/rtape/tape1_BEST /dev/rtape/tape1_BESTn
/dev/rtape/tape1_BESTb /dev/rtape/tape1_BESTnb
# hpvmmodify -P guest1 –a tape:avio_stor:0,4:attach_path:0/7/1/1.0x500104f00048b29e.0x0
To migrate from AVIO back to VIO for guest1, do the following:
# hpvmstatus -P guest1 –d
:
[Storage Interface Details]
disk:scsi:0,2,0:lv:/dev/vg00/rlvol1
disk:scsi:0,2,1:disk:/dev/rdisk/disk28
tape:avio_stor:0,4,0:attach_path:0/7/1/1.0x500104f00048b29e.0x0
disk:avio_stor:0,4,1:lv:/dev/vg01/rlvol1
disk:avio_stor:0,4,2:lv:/dev/vg01/rlvol2
disk:avio_stor:0,4,3:lv:/dev/vg01/rlvol3
disk:avio_stor:0,4,4:disk:/dev/rdisk/disk20
dvd:avio_stor:0,4,5:file:/fdev/0x500000e012afb8d2/file2
:
# hpvmmodify –P guest1 –d tape:avio_stor:0,4,0:attach_path:0/7/1/1.0x500104f00048b29e.0x0
# hpvmmodify -P guest1 -m hba:scsi:0,4
# ioscan -kfnNH 0/7/1/1.0x500104f00048b29e.0x0
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
lunpath 21 0/7/1/1.0x500104f00048b29e.0x0 eslpt CLAIMED LUN_PATH LUN path for tape1
# hpvmmodify -P guest1 -a tape:scsi:0,4:attach:/dev/pt/pt_tape1
6.1.3.5 Limitations
Although SCSI devices appear to a guest as Ultra320 SCSI controllers claimed by the MPT driver,
this is an emulation. There are several differences from using a real device. Specifically:
• You cannot upload or download firmware for emulated devices.
• Although HP-UX commands such as mptutil(1M) and mptconfig(1M) do not fail when run
in a guest, they do not always return the same information as they would when referencing
a physical device.
• The EFI drvcfg command does not fail when run in a guest, but it returns no useful data.
The AVIO attached devices feature has the following limitations:
• Integrity VM does not support the hpvmmodify -m hba option when attached devices
are present under the adapter. The hpvmmodify -m hba option allows you to change
the adapter type from scsi to avio_stor and vice versa. Remove the attached devices from the
adapter prior to issuing the command. For information about manual migration, see
Section 6.1.3.4 (page 89).
• 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 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.
• 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.
• 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:
# timex diskinfo /dev/rsdk/c1t14d0:
diskinfo: can't open /dev/rdsk/c1tl4d0: No such device or address
90 Creating Virtual Storage Devices