HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

The following example shows that the second guest cannot be started:
# hpvmstart -P guest2
hpvmstart: ERROR (host): Device: '0/4/1/0.0x500104f0004732da.0x0' associated with guest: 'guest2' conflicts
with device:
'0/4/1/0.0x500104f0004732d9.0x0' associated with guest: 'guest1'. Both guests cannot be booted at the same
time because both
devices use the same initiator, even though SHARE_LUNPATHS is set to YES.
HPVM guest guest2 configuration problems:
Warning 1 on item 0/4/1/0.0x500104f0004732da.0x0: Device file '0/4/1/0.0x500104f0004732da.0x0' in use by
another guest.
These problems may prevent HPVM guest guest2 from starting.
hpvmstart: Unable to continue.
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.
NOTE: If the guest operating system version is prior to HP-UX 11i v3 0809 (that is, 11i v3 0709
or 0803), a guest LUN might not appear after a delete and add. For example, this issue might
occur with the following sequence of events::
1. In the guest, execute rmsf for the lun path ( lunpath Class in ioscan display).
2. In the VM Host, delete the lun entry from the guest's configuration using the hpvmmodify
command.
3. In the VM Host, add the lun entry back to the guest's configuration using the hpvmmodify
command.
4. In the guest ioscan, the lun (which was deleted and added back) does not appear.
Perform the following workaround:
1. In the guest, rmsf the target path (tgtpath Class in ioscan display) corresponding to the lun
path.
2. In the guest, perform an ioscan.
6.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
6.1 Introduction to Integrity VM Storage 89