HP Matrix Operating Environment Software - Manual (Page 63)

Workaround
To maintain the process placements across redeploys, use gWLM's application records or user
records when creating or editing your workload definitions in gWLM.
Sizes/allocations less than policy minimums for Virtual Machines
The sizes or allocations for virtual machines in a deployed SRD can appear to be less than their
policy minimums.
Workaround
Wait a few minutes, since it can take several minutes for gWLM to recognize a virtual machine
transition between the states of off and on.
Changes in sizes in Discovery
When a VSP with vPars is added to an SRD, the total size that is displayed during discovery might
differ from the sum of sizes of the compartments. This is because of the free cores in the guest pool
of the VSP that do not belong to any vPar.
Workaround
Wait for the SRD to be deployed. The sizes will be proper after deployment.
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 might get the following error when attempting to complete the Workload
& Policies step of the Manage Systems & Workloads Wizard:
The value '0' specified for 'Total Size' must be a positive integer
value.
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.
Workaround
You can manage the workloads using compartments based on fss groups (which have a smaller
minimum size), or add resources to the partition or SRD, to fulfill the pset minimum size requirements.
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.
Discovery does not show current information for stopped virtual machines
Global Workload Manager discovery does not always report current information for stopped
virtual machines. Specifically, when a virtual machine is stopped and the number of vCPUs is
changed, gWLM discovery does not show the changed number of vCPUs. Instead, it shows the
number of vCPUs from the virtual machine's most recent start.
Workaround
Start the virtual machines before performing discovery.
Documentation or minor issues 63