HP Integrity Virtual Machines 4.2.5 - HP Business Support Center

◦
If the LV or file backing store file name is 55 characters long and the guest is a HP-UX
11i v3 guest, guest panic or disk dsf name change is seen on subsequent guest reboots.
◦ When guest storage applications (for example, dd, diskinfo, and so on) attempt to access
a device special file, an “Invalid argument” error might be returned. This problem is seen
on HP-UX 11i v2 and HP-UX 11i v3 guests with GuestAVIOStor versions earlier than
11.23.0903 and 11.31.0903 respectively. In this case, the HostAVIOStor version is
11.31.0903 or 11.31.0909.
• The following fixes are included in the GuestAVIOStor version HP–UX 11i v3 1003 driver:
◦
Unload of HP-UX 11 v3 guest AVIO driver (gvsd) might cause guest to panic.
◦ When HP-UX 11i v3 guest was cold installed, DSF name changed after HBA migration
between VIO and AVIO
◦ The scripts, avio-vio and the gvsd-conf were delivered incorrectly on the HP-UX
11i v3 guest.
8.2.4 GuestAVIOStor HBA Driver (gvsd) DLKM
The GuestAVIOStor HBA driver (gvsd) DLKM supports dynamic loading and unloading of the driver
starting with version B.11.31.0903.01 and the B.11.31.0903 version of the HostAVIOStor HBA
driver.
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
:
:
80 Storage Information