HP Integrity Virtual Machines Manager 4.3 Release Notes

1. The following error message is displayed on Matrix Operating Environment:
The required selection for this action is missing. select the object
on which you wish to perform the action and entry. This can be caused
if the guest has been deleted from the host."
2. A Java error is displayed on the VM Manager page after remote console is configured through
CLI.
Workaround
Restart the Matrix OE visualization and VM Manager page.
VM Manager displays wrong state of AMR
When AMR is enabled for a VM in the On state, the AMR enabled field in VM General Properties
page displays “No” instead of “Yes”. This is a display error.
Workaround
To view the correct AMR state, run hpvmstatus -P <vmname> -r on the CLI.
Incorrect VM memory value limitation check
The memory entitlement size must not be less than the minimum memory size and not more than
the initial target memory size. If the dynamic memory entitlement and the initial target memory size
are modified at the same time, and if the memory entitlement is greater than the initial target
memory size, VM Manager displays an error. This is because the limitation check is done based
on the current value and not the value that will be set.
Workaround
Set the initial target memory size and after this modification is effective, modify the memory
entitlement size.
VM Manager does not display utilization data for OpenVMS guests
Applies to usage with: Both Matrix Operating Environment and HP SMH Standalone
The utilization data for OpenVMS guests may not be visible after the first installation of the
OpenVMS operating system or after rebooting the OpenVMS guest systems. This is because, by
default, the TCP/IP and WBEM Provider services do not start automatically after rebooting the
OpenVMS guest machine.
Workaround
The TCP/IP, the WBEM Services, and the Utilization Provider products are not installed by default
on an OpenVMS guest. Ensure that the TCP/IP, the WBEM Services and the Utilization Provider
products are installed, configured, and started on the guest. After rebooting the guest, check if the
TCP/IP and WBEM Services have been started. If not, restart TCP/IP and/or WBEM Services
manually or add the command in the startup script so that they start automatically when the
OpenVMS guest reboots. For more information, see the OpenVMS documentation on setting up
TCP/IP and WBEM Provider services.
VM Manager screens might incorrectly identify or omit USB backing devices
Applies to usage with: Both Matrix Operating Environment and HP SMH Standalone
Integrity VM 4.x allows a USB DVD or CD drive to be used as the backing devices for a virtual
DVD or CD in a virtual machine. However, in the HP-UX 11i v3 September 2008 Operating
Environment Update Release (OEUR) and earlier, the drivers for the USB devices are not completely
integrated into the HP-UX 11i v3 agile mass storage stack. They have neither a persistent device
special file nor a LUN hardware path. In addition, they have an ioscan description that might
not correctly indicate the type of device. For example, ioscan might report "USB SCSI Stack
10 Limitations and known issues