HP Integrity Virtual Machines Release Notes Version A.03.50

WBEMServices.WBEM-CORE-COM A.02.00.11 WBEM Services COM
Fileset for hp Integrity servers and hp 9000 servers
WBEMServices.WBEM-MAN A.02.00.11 WBEM Services MAN
Fileset
WBEMServices.WBEM-MX A.02.00.11 WBEM Services MX
fileset
2.1.7 VMMGR V3.0 Does Not Support Integrity VM V3.5 AVIO Functionality
Integrity Virtual Machine Manager Version 3.0 and earlier versions do not support AVIO
functionality. You can use Integrity VM Manager to view and manage virtual machines with the
following restrictions:
• When creating or modifying a virtual machine, you can add only VIO storage or network
devices from Integrity VM Manager. To add an AVIO device or change an existing device
from VIO to AVIO, use the hpvmmodify(1M) command after the VM has been created.
• There is no indication on any screen whether a particular virtual I/O device, virtual switch,
or physical device supports AVIO, with one exception. On the VM Host and VM properties
network tabs, AVIO virtual network interfaces appear with the numeral "14" replacing the
word "LAN" in the first line of the box representing the virtual network interface.
• If a virtual machine contains an AVIO storage device, displaying the VM Host or VM
Properties storage tab results in a stack trace. If you want to use AVIO storage devices with
Integrity VM Manager Version 3.0, consult HP technical support for a fix for this issue. After
the issue has been fixed, AVIO virtual storage devices will appear with the annotation
"Unknown Storage Adapter" instead of "SCSI".
2.1.8 VxVM Device Path Not Valid Error on HP-UX 0803
Installing or updating HP-UX 0803 might result in the following VxVM error:
NOTICE: VxVM vxdmp V-5-0-34 added disk array OTHER_DISKS, datype = OTHER_DISKS
VxVM vxdisk ERROR V-5-1-5433 Device disk1_p2: init failed:
Device path not valid
* smapi listener returned "ACTION_FAILURE" for message "CREATE_GROUP"
The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]):
This error is caused by a 32–byte VxVM length limitation on disk device ID information. Integrity
VM virtual disks report back a standard T10 device ID created with the 8–byte T10 HP identifier
followed by a null terminated string of the backing store name. For example, the resource
statement, "disk:scsi::lv:/dev/vx/rdsk/lvrackA/disk1", results in the T10 device
ID, "HP /dev/vx/rdsk/lvrackA/disk1". Therefore, to avoid this error, the length of the
backing store name must not exceed 23 characters.
2.1.9 HP-UX Patches Required in the VM Host
Table 2-1 lists the patches that are required in the VM Host system running Integrity VM A.01.00
and later. For patches required for earlier versions of Integrity VM, consult the Release Notes
document for that version. For the most up-to-date patch list, see the HP ITRC website: http://
www.itrc.hp.com.
Table 2-1 VM Host Patches
CommentDescription/ImpactFixAffected Integrity VM
Version
Affected HP-UX (VM
Host) Version
This patch
incorporated into 0512
update.
FSSPHKL_33052
(11.23.0512)
A.01.20 or later11i v2 0505 through
0509
Resolves panic on host.Bug fixPHKL_34082
(11.23.0609)
A.01.20 or later11i v2 0505 through
0606
2.1 Installing Integrity VM 21