HP Integrity Virtual Machines 4.3: Release Notes (5900-2265, May 2012)

8.2.5 Agile DSFs Change in HP-UX 11i v3 Guest When Migrating Disks Between
scsi and avio_stor
GuestAVIOStor version B.11.31.0810 or higher version fixes the change of agile device names
in the guest OS when HBA is migrated between scsi (VIO) and AVIO storage. Follow these steps
while changing the configuration of a guest HBA between VIO and AVIO. This is to ensure that
agile disk device files under the modified HBA remain the same. If individual devices are moved
between AVIO and VIO using hpvmmodify delete and add, the agile device name will change.
The old device name can be restored using scsimgr or the affected applications modified to use
the new device name. Perform the following steps:
• Boot the guest with the GuestAVIOStor 11.31.0810 depot. (This step is required even if you
do not have any AVIO devices configured.)
• Shut down the guest gracefully using the shutdown(1m)command.
• Migrate the HBA from VIO to AVIO (or AVIO to VIO) using the hpvmmodify command.
• Boot the guest and verify that all the agile device files are as expected.
The following messages might appear on the guest console during the first boot after a scsi hba
has been changed to avio_stor hba. The LVM error messages are harmless. Use the lvlnboot
–R command to fix the boot information on the root logical volume and eliminate these boot-time
messages:
LVM: Failure in attaching PV (dev=0x3000006) to the root volume group.
The physical volume does not exist, or is not configured in the kernel.
LVM: Activation of root volume group failed
Quorum not present, or some physical volume(s) are missing.
LVM: Scanning for Root VG PVs (VGID 0xef4fbb14 0x48acd569)
LVM: Rootvgscan detected 1 PV(s). Will attempt root VG activation using
the following PV(s):
0x3000003
LVM: Root VG activated
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 4194304 Checking root file system.
file system is clean - log replay is not required Root check done.
Create STCP device files
:
:
GuestAVIOStor: Instance numbers for AVIO/VIO disks fixed due to HBA type changes.
GuestAVIOStor: Refer to /etc/opt/gvsd/files//gvsd.log for details.
8.2.6 AVIO Limitations
The following sections describe the current limitations using AVIO. For a complete list of AVIO
limitations, see the HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration
manual on the BSC website:
http://www.hp.com/go/hpux-hpvm-docs
8.2.6.1 Presenting a Logical Volume Created on iSCSI Devices as AVIO Backing Store to a Guest
Not Supported
March 2011 Release
Presenting a Logical Volume that is created on an iSCSI device as an AVIO backing store to a
guest is not supported.
8.2.6.2 Online Modification of AVIO Devices Might Fail
March 2011 Release
The following list provides reasons for online modification of AVIO device failure and their solutions:
8.2 Changes and Issues in This Release 39