HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

— Adjust the entitlements of those virtual machines that are on so that the CPUs are not
oversubscribed.
— Stop one or more virtual machines until those still on do not oversubscribe the CPUs.
• Unmanaging a Virtual Machine That Is On Leaves SRD Undeployed When attempting to
unmanage a virtual machine that is started, the SRD can be undeployed, even though the
following message is displayed:
The virtual machine VM_name on host hostname is on but does not have
an associated gWLM policy. Please turn the virtual machine off, or
apply a gWLM policy to provide the necessary resources.
Workaround Turn off the virtual machine and redeploy the SRD that contained it.
• Log File Extensions Other than .log.0, .log.1, and .log.2 Global Workload Manager is
designed to use the file extensions .log.0, .log.1, and .log.2 for its log files. Java file
locking is used to ensure that only one gWLM process is updating a log file at any given
time. Starting with Java 1.4.2.06, the file locking allows the creation of files with extensions
of the form .log.0.n, where n is some integer.
Workaround If you are using Java version 1.4.2.06 or later and you want to check the logs
for errors, use the following command to see which files have recent error messages:
# /bin/ls -ltr /var/opt/gwlm/*log*
You can then use /usr/bin/tail to view messages in recently updated log files.
If you are sending the log files to HP Support, create a tar file using the following commands:
# cd /
# tar cvf /tmp/gwlmlogs4support.tar var/opt/gwlm/*log*
Then send the /tmp/gwlmlogs4support.tar file to HP Support.
• Advanced Reports Cannot Process Workloads with Spaces at Start/End of Name Starting
with gWLM A.03.00.00, workload names could contain spaces. However, the gwlmreport
utility, which generates advanced reports, cannot process workload names that start or end
with spaces.
Workaround Rename your workloads to not start or end with spaces.
• gwlmreport ovpafeed --dataversion Problems Running either of the following
commands:
— gwlmreport ovpafeed
— gwlmreport ovpafeed --dataversion=4.0
results in an error.
Workaround Use the following commands to set up the feed and extract data:
— gwlmreport ovpafeed --setup --dataversion=3.0
— gwlmreport ovpafeed --dataversion=3.0
• Error When Securing Communications You may see a message similar to the following
one when attempting to secure gWLM communications:
keytool error: java.lang.Exception: Key password must be at least 6 characters
unable to create keystore /etc/opt/gwlm/certstor/gwlm.keystore
unable to create the gwlm keystore at /opt/gwlm/bin/gwlmsslconfig line 184.
Workaround Try securing communications again.
HP Integrity VM Manager
Limitations
• VM Manager Does Not Fully Support Nested APA Devices Integrity VM version 3.5 supports
nested Automatic Port Aggregation (APA) backing devices for virtual switches, but VM
HP Integrity VM Manager 51