HP-UX Workload Manager A.03.01 Release Notes for HP-UX 11i v1 and HP-UX 11i v2
HP-UX Workload Manager Release Notes
Compatibility information and installation requirements
25
Compatibility of WLM’s virtual partition management and
Instant Capacity / PPU
If you have Instant Capacity or Pay Per Use (PPU) software installed, use WLM’s 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’s 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’s 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’s partition management and PPUTK
Do not use WLM’s partition management (virtual partition or nPartition management) and
the Pay Per Use Toolkit (PPUTK) tool utilitydc at the same time.
Compatibility of WLM 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 CPUs across HP-UX
Virtual Partitions or nPartitions, or for activating Temporary Instant Capacity cores or Pay
Per Use CPUs. (WLM will not run with FSS groups or PSETs on Integrity VM Hosts where
guests are running.)
WLM runs inside an Integrity VM but will not support Pay Per Use, vPar, and Instant
Capacity integration. However, Integrity VM will take advantage of CPU resources added to
the Integrity VM Host by Pay Per Use, Instant Capacity, and Temporary Instant Capacity. 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, refer to the following web site and navigate to the
"Solution components" page:
www.hp.com/go/vse