HP-UX Workload Manager A.03.05.xx Release Notes for HP-UX 11i v3

Compatibility with HP Integrity Virtual Machines
WLM supports HP Integrity Virtual Machines (Integrity VM). You can run WLM both on the Integrity
VM Host and in an Integrity VM (guest), but each WLM runs as an independent instance. To run
WLM on the Integrity VM Host, you must use a strictly host-based configuration—a WLM
configuration designed exclusively for moving cores across HP-UX Virtual Partitions or nPartitions,
or for activating Temporary Instant Capacity (TiCAP) cores or Pay per use (PPU) cores. (WLM will
not run with FSS groups or PSETs on Integrity VM Hosts where guests are running.) In addition,
ensure that the minimum number of cores allocated to a WLM host is greater than or equal to the
maximum number of virtual CPUs (vCPU count) assigned to each VM guest. Otherwise, VM guests
with a vCPU count greater or equal to WLM’s minimum allocation could receive insufficient resources
and eventually crash. For example, if an Integrity VM host has 8 cores and three guests with 1,
2, and 4 virtual CPUs, respectively, your WLM host should maintain an allocation of at least 4
cores at all times. You can achieve this by using the WLM hmincpu keyword.
WLM runs inside an Integrity VM but will not support PPU, vPar, and Instant Capacity (iCAP)
integration. However, Integrity VM will take advantage of cores added to the Integrity VM Host
by PPU, Instant Capacity, and TiCAP. As noted previously, WLM must continue allocating at least
as many cores as the maximum number of virtual CPUs in any VM guest on the system. In addition,
when running WLM inside an Integrity VM, you should specify a WLM interval greater than 60
seconds. This helps ensure a fair allocation of CPU resources for FSS groups.
For more information on Integrity VM, go to the following location and navigate to the “Solution
components” page:
http://www.hp.com/go/vse
Compatibility of WLM virtual partition management and
Instant Capacity / PPU
If you have Instant Capacity (iCAP) or Pay per use (PPU) software installed, use WLM virtual
partitions management only if you have vPars version A.03.01 or later.
If you have a vPars version prior to A.03.01, using WLM virtual partition management may cause
an Instant Capacity core to be automatically enabled without customer authorization. If this situation
occurs, please contact your HP representative.
With vPars version A.04.01 or later, use Instant Capacity v7 or later.
Compatibility of WLM virtual partition management and certain CPU
bindings
Do not use cell-specific CPU bindings or user-assigned CPU bindings on virtual partitions you are
going to manage with WLM.
Compatibility of WLM partition management and PSETs
WLM now supports simultaneous management of partitions (virtual partitions or nPartitions) and
PSET-based workload groups. Such support requires the following:
• If Instant Capacity (iCAP) is available on the complex, it must be v7 or later
• If HP-UX Virtual Partitions (vPars) is on the complex, it must be v4 (A.04.01) or later
• If Pay per use (PPU) is on the complex, it must be v7 or later
Compatibility of psrset and PSETs
When WLM is managing PSETs, do not use the psrset command to change settings.
Compatibility with HP Integrity Virtual Machines 17