HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration
NOTE: After the user adds more than one attached lunpath to a particular device to one or
more guests, each device database lunpath entry has an AGILE_DSF attribute that points to the
agile-named parent DSF. If the user wants to allow guests to boot at the same time when they
use different lunpaths to the same device, SHARE_LUNPATHS=YES is set on the entry to which
that AGILE_DSF points.
Two different guests can use different lunpaths to the same device at the same time
(SHARE_LUNPATHS=YES) if the paths use DIFFERENT initiators; however, Integrity VM blocks
the use of different guests using different lunpaths at the same time if they use the SAME initiator.
SHARE_LUNPATHS=YES can still be set when potential initiator-sharing conflicts exist. The
hpvmstart command blocks the guests from booting when the same-initiator conflict (of using
different paths) exists.
7.1.3.4 VIO to AVIO Migration with Attached Devices
Integrity VM does not support automatic migration of a virtual scsi (VIO) adapter containing
attached devices to avio_stor (AVIO) adapter. To do the migration manually, follow these steps:
1. Shut down the guest.
2. Identify the virtual HBA that needs to be migrated using the hpvmstatus command.
3. Make note of the attached devices under the virtual HBA.
4. Delete the attached devices under the virtual HBA using the hpvmmodify command.
5. Migrate the remaining non-attached devices on the adapter by running the hpvmmodify
command with the -m hba option.
6. Find the adapter specific device part of the resource specifier. See Section 7.1.3.1 (page 95).
7. Add previously deleted attached devices using the hpvmmodify command.
For example, to migrate from VIO to AVIO 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:scsi:0,4,0:attach:/dev/pt/pt_tape1
disk:scsi:0,4,1:lv:/dev/vg01/rlvol1
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
7.1 Introduction to Integrity VM Storage 99