HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

1. In the file /etc/opt/gwlm/conf/gwlmcms.properties (HP-UX) or
install-path\VirtualServerEnvironment\conf\gwlmcms.properties
(Windows), increase the CMS database cache size by increasing the value of the
com.hp.gwlm.cms.cachesize property by 25%. (The cache is more memory efficient
if the size is near a power of 2. If your target cache size is close to a power of 2, round
it up to the next power. For example, if your target cache size is 60,000, round it up to
66,000.)
2. Stop and restart gwlmcmsd using the following commands.
NOTE: Stopping gwlmcmsd disables Virtualization Manager and Capacity Advisor.
# gwlmcmsd --stop
# gwlmcmsd
• Deleting Workloads Takes a Long Time Once a request to delete a workload is issued, it
can take a long time (several minutes) to complete the deletion.
Workaround Remove old historical monitoring and configuration data from the gWLM
database by entering the following command:
# gwlm history --truncate --truncate=<CCYY/MM/DD>
If you prefer not to trim the database, you can delete multiple workloads simultaneously
using the gwlm delete command.
For more information, see gwlm(1M).
• Integrity VM Prevents Discovery of psets and fss Groups When the gWLM agent is installed
on a system that has Integrity VM installed, discovery operations report only Integrity VM
compartments even if psets and fss groups are present.
Workaround To discover psets or fss groups on the system, must remove Integrity VM.
• Only Workloads with Managed Siblings Can be Added to SRDs with Nested Partitions
Using the gWLM command-line interface, you cannot add a workload to an SRD that has
nested partitions unless a sibling of that workload is already managed in that SRD.
Workaround This is not an issue when you use the gWLM interface in HP SIM. Simply
follow the instructions in Step 1 of the Manage Systems and Workloads wizard (reached by
selecting Create→Shared Resource Domain), and select the set of hosts to include in a
single SRD.
• Unable to Remove Workload from Nested Partitions SRD When attempting to remove the
last (default) fss group from an SRD with nested partitions, you might encounter a message
that includes the following text:
Unable to remove workload workload_name: Attempting to remove a
compartment with an unachievably low Fixed policy size. Increase
the Fixed policy resource amount and try again.
Workaround Undeploy the SRD and delete it. Then create a new SRD without the fss
group that you were trying to remove.
• Combining psets and virtual partitions When using psets on virtual partitions, assigning
CPUs to virtual partitions by either path or cell specification can result in processes losing
their processor set affiliations when CPUs are removed.
Workaround Two workarounds are available:
— Do not assign CPUs to virtual partitions by either path or cell specification.
— Set the gWLM policy minimum for pset 0 (the default/OTHER workload) to be greater
than or equal to the sum of path-specific CPUs and cell-specific CPUs.
42 Known Issues