HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide

Missing historical data (gWLM CMS daemon/service restarted)
You might have blank sections of a historic report for a workload, or you might see the following
error message when displaying historic data for a workload:
There is no gWLM historical data for the workload MyWorkload.wkld. The
workload has never been managed by gWLM, or the historical data has
been removed.
Because of caching gWLM historic data in System Insight Manager, if the gWLM CMS
daemon/service is restarted after initially viewing historic data, the interface incorrectly reports
that there is no data available to view or fails to load portions of the data.
Workaround
Perform the following steps:.
1. Log out of System Insight Manager
2. Log in to System Insight Manager (again)
3. Generate the historic report (again)
Negative current size for NONVM
If the CPUs on a VM Host are oversubscribed when you deploy an SRD on that host, gWLM shows
current size for NONVM as a negative value.
Workaround
Two options are available:
• 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 VM or vPar that is ON leaves SRD undeployed
When unmanaging a started VM or vPar on VSP, 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 VM or vPar and redeploy the SRD that contained it.
Excluding a VM or vPar that is ON during the modification of the SRD leaves the
SRD undeployed
When a started VM or vPar on VSP is excluded when modifying the SRD, the following message
is displayed leaving the SRD undeployed:
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.
When this error message is displayed and the user cancels the modification process, the SRD gets
undeployed.
Workaround
Always ensure that VMs and vPars that are ON are included as part of the SRD. Else, turn off the
VM or vPar, and redeploy the SRD that contained it.
68 Global Workload Manager known issues