HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes
with entitlements specified in percentages. (That is, do not manage virtual machines with
entitlements specified in CPU cycles.)
To obtain older versions of the gWLM agent, and for assistance with this configuration,
contact HP at the following email address: gwlmfeedback@rsn.hp.com.
• Compatibility with PRM and WLM You cannot use gWLM with either Process Resource
Manager (PRM) or Workload Manager (WLM) to manage the same system at the same time.
Attempts to do so result in a message indicating that a lock is being held by whichever
application is actually managing the system. To use gWLM in this situation, first turn off
the application holding the lock.
For PRM, enter the following commands:
# /opt/prm/bin/prmconfig -d
# /opt/prm/bin/prmconfig -r
For WLM, enter the following command:
# /opt/wlm/bin/wlmd -k
• Compatibility with Global Instant Capacity For information on restrictions when using
gWLM with Global Instant Capacity, visit http://docs.hp.com/en/vse.html and locate the
white paper Using Global Workload Manager with Global Instant Capacity.
• 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.
• Upgrade of Partition-Based SRDs Requires Rediscovery If you are using gWLM and you
have either of the following types of partition-based SRDs, and you have upgraded the
gWLM agents in the partitions from gWLM A.01.x to gWLM 4.0, you cannot add other
partitions in the same complex to the SRD:
— A vPars-based SRD inside an nPartition
— An nPartition-based SRD using iCAP
Workaround Use the following procedure on the CMS to reestablish the SRD:
1. With the SRD deployed, rediscover the SRD. For a vPars-based SRD, enter the following
command:
# gwlm discover --type=vpar \
--file=/tmp/myfile.xml hosts
For an nPartition-based SRD, enter the following command:
# gwlm discover --type=npar \
--file=/tmp/myfile.xml hosts
In these commands, replace hosts with a space-separated list of the partitions in the
SRD.
2. Make the following adjustments to the /tmp/myfile.xml file, as explained in
gwlmxml(4):
38 Known Issues