HP Integrity Virtual Machines Manager 4.1.1 Software: Release Notes

2 VM Manager limitations and known issues
This chapter includes the following information in the sections indicated:
SectionInformation
“Recent issues fixed in this release (A.4.1.1)” (page 7)Recent issues fixed in this release (A.4.1.1.83278)
“Limitations and restrictions” (page 7)Limitations and restrictions
“Major issues” (page 7)Known major issues that affect functionality or usability of
VM Manager and any ways you can work around these
issues
“Minor issues” (page 7)Known minor issues that do not affect functionality or
usability significantly and any ways you can work around
these issues
“Documentation errors and limitations” (page 9)Known errors, omissions, and limitations in the VM
Manager documentation (including help).
Any limitations or issues that are HP SMH specific are noted as such.
Recent issues fixed in this release (A.4.1.1)
This section lists problems found in an earlier version of VM Manager A.4.1.1 and that have been
fixed for this current release. There are no known issues that have been fixed for this release.
Limitations and restrictions
This section describes limitations or restrictions in this release of VM Manager. For this release,
there are no known limitations or restrictions.
Major issues
This section describes known issues that significantly affect functionality or usability of VM Manager.
For this release, there are no known major issues.
Minor issues
This section describes known issues that do not have a significant impact on functionality or usability
of VM Manager. Suggestions for working around these issues are included.
VM Manager does not display utilization data for OpenVMS guests
Applies to usage with: Both Insight Dynamics 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.
Recent issues fixed in this release (A.4.1.1) 7