HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide

# /opt/wlm/bin/wlmd -k
Rare incompatibility with virtual partitions
Depending on workload characteristics, gWLM can migrate CPU resources rapidly. This frequent
migration can potentially, although very rarely, produce a race condition, causing the virtual
partition to crash. It can also produce a panic, resulting in one or more of the following messages:
No Chosen CPU on the cell-cannot proceed with NB PDC.
or
PDC_PAT_EVENT_SET_MODE(2) call returned error
Workaround
Upgrading to vPars A.03.04 resolves this issue.
With earlier versions of vPars, you can work around this issue as follows: Assign (using path
assignment) at least one CPU per cell as a bound CPU to at least one virtual partition. (It can be
any virtual partition). This ensures that there is no redesignation on CPU migrations. For example,
if you have four cells (0, 1, 2, 3), each with four CPUs (10, 11, 12, 13) and four virtual partitions
(vpar1, vpar2, vpar3, vpar4), you could assign 0/1x to vpar1, 1/1x to vpar2, 2/1x to vpar3,
and 3/1x to vpar4, where x is 0,1,2,3.
Workloads in gWLM do not follow associated Serviceguard packages
With the exception of virtual machines, a workload can be managed by gWLM in only one
deployed SRD at a time. As a result, if a workload is directly associated with a Serviceguard
package (using the selector in the Workload Definition dialog), gWLM can manage it on only one
of the hosts on which it might potentially run. However, management of such a workload might
disrupt the HP Matrix OE visualization and Capacity Advisor tracking of the workload utilization
between cluster members. Thus, it is recommended that you not directly manage a workload
associated with a Serviceguard package.
Workaround
For all hosts to which a workload associated with a Serviceguard package might fail over, you
must apply a policy to an enclosing operating system instance (virtual partition or nPartition). You
can use a gWLM conditional policy to change the resource allocation depending on which packages
are present. This enables you to control the resource allocation of the enclosing operating system
instance and still monitor the workload via HP Matrix OE visualization.
Host name aliases are not supported
Host name aliases are not supported by gWLM. Only canonical DNS host names (fully qualified
domain names) are supported.
Workaround
Use only canonical DNS names when configuring gWLM through either System Insight Manager
or an XML file used with the gwlm command.
Making a configuration change to a large SRD is slow
Changes made to the configuration of a large SRD that is deployed might take a long time (several
minutes) to take effect.
Workaround
There is no workaround. The amount of time needed to complete a change depends on the time
it takes to communicate with all the compartments in the SRD.
Events for gWLM CPU migration can affect System Insight Manager CMS performance
The HP products System Fault Management (SFM) and Event Monitoring Service (EMS hardware
monitors in particular) generate events, or indications, when CPUs are migrated. Depending on
workload characteristics, gWLM can migrate CPUs rapidly. Over time, this frequent migration can
58 Global Workload Manager known issues