HP PRM Version C.03.06 release notes - (March 2012)

Table 4 HP-UX 11i v2 (B.11.23) patch for WLM (continued)
DescriptionHP-UX 11i v2 patch*
NOTE: Install these patches at the same time.
These patches help ensure each job within a FSS-based PRM group gets a more equal
share of the group’s entitlement than it would under HP-UX semantics.
PHKL_33604,
PHKL_33605
Addresses a libc defect relating to ps, cron, login, and other such commandsPHCO_34599
* These patches may have been superseded. You can use the patches listed here or their superseding
patches.
Compatibility with HP Integrity Virtual Machines
HP Integrity Virtual Machines (Integrity VM) is a robust soft partitioning and virtualization technology
that provides operating systems isolation, shared CPU (with sub-CPU granularity), shared I/O, and
automatic, dynamic resource allocation. It is available for HP-UX 11i v2 running on HP Integrity
servers.
Given a system with Integrity VM installed, you can run PRM inside any of the virtual machines;
however, you cannot run PRM on the VM Host as the vm_fssagt already controls FSS groups
on behalf of Integrity VM.
NOTE: Do not specify disk bandwidth records for configurations used inside virtual machines.
Compatibility with processor sets (PSETs)
PRM allows you to define PRM groups based on PSETs.
NOTE: When you have PRM groups based on PSETs, disable PRM to perform any of the following
operations:
• Modify the PSETs manually using the psrset command
• Adjust core (CPU) counts in virtual partitions using the vparmodify command
• Adjust Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP), or Pay Per Use resources
using the icapmodify or ppuconfig commands
• Perform online cell operations, using parolrad or any other interface, while PRM is managing
the system (For more information, see the WARNINGS section in prmconfig(1).)
Compatibility with WLM
You can have distinct PRM and WLM configurations in use at the same time. For example, the
WLM configuration could be managing only the migration of CPU resources across virtual partitions
or nPartitions. For more information, see the WLM Release Notes.
When upgrading WLM, be careful of the order of upgrades, as explained in “Upgrading or
installing PRM before upgrading WLM from C.03.00 or earlier can cause WLM to fail swverify
checks” (page 19).
Compatibility with gWLM
PRM and HP Global Workload Manager (gWLM) should not be used to manage the same system
at the same time. Using these products to control resources at the same time may cause inconsistent
behavior and undesirable performance.
Compatibility with HP Integrity Virtual Machines 13