HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

Workaround Update the CMS version. This update also installs the corresponding agent.
(Because gWLM requires all managed nodes in an SRD to have the same agent version, you
must update the agents on any other managed nodes that could be in an SRD that includes
the CMS. For information about performing this update, see the VSE Management Software
Installation and Update Guide.
• gWLM Fails to Start with Certain Time Zone Settings gwlmcmsd and gwlmagent can fail
to start with certain time zone settings. The following message is displayed in the
gwlmagent.log.0 file or the gwlmcmsd.log.0 file when you attempt to invoke either daemon:
Unable to call method, 'main', with signature,
'([Ljava/lang/String;)V', in class, 'com/hp/gwlm/node/Node'.
Exception in thread "main"
Workaround Use Java 1.5.0.12 or later.
• gWLM Commands Core Dump Attempts to run gwlm commands result in core dumps
when /var is full.
Workaround Make space available in /var.
• Unable to Create New Native Thread A message containing the following text might be
displayed:
... unable to create new native thread
Workaround This problem occurs because the following kernel parameters are set too
low:
— max_thread_proc
Set max_thread_proc to at least 256.
— nkthread
Set nkthread to allow for your max_thread_proc value as well as the number of
threads needed by all the other processes on the system.
Minor Issues
• “Force Undeploy” Link Requires gWLM Agents to be Running to Undeploy Certain SRDs If
any gWLM agents in an SRD with nested partitions are not running when you click the
Force Undeploy link in the Shared Resource Domain view, you are redirected to the SRD
Modify screen so you can restart the gWLM agents and complete a clean undeploy. If the
gWLM agents cannot be started or are not reachable, you cannot use the undeploy operation
from the gWLM interface in SIM.
Workaround Use the gwlm command: gwlm undeploy --srd=SRD_name --force
• Starting Management of Monitored workloads with pset Compartments If you attempt to
manage a set of monitored workloads by applying a policy and managing them with pset
compartments, you may get the following error:
The value '0' specified for 'Total Size' must be a positive integer value.
when attempting to complete the Workload & Policies step of the Manage Systems &
Workloads Wizard.
This message is displayed when you attempt to manage a set of pset compartments that
require more cores than are available on the managed node. A pset has a minimum size of
one core, so you need at least as many cores as workloads you are attempting to manage.
The Total Size field cannot be calculated when there are not enough resources on the system
to manage the set of monitored workloads in pset compartments.
40 Known Issues