HP PRM Version C.03.03.01 Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

PRM Release Notes
Known problems and workarounds
Chapter 1 21
Unable to achieve CPU entitlement due to number of processes
Issue
PRM provides a PRM group its entitlement on an SMP system with
Hyper-Threading disabled by granting the group its entitlement on each
core. If the group does not have at least one process for each core, PRM
compensates by proportionally increasing the PRM group’s entitlements on
cores where it does have processes. For example, for a PRM group with a
single-threaded process, a 10% entitlement of four cores results in a 40%
entitlement on one core.
Assume this same PRM group were allocated 50% of the four cores. PRM
would give the group an entitlement of 100% on two cores. However, because
the group has only the one thread, it can use only one core, resulting in a
25% entitlement.
Workaround
There is no workaround. However, be aware of how your applications run so
that you do not give them resource entitlements they cannot use.
Secure Resource Partitions:
Blocked port on a virtual network interface
Issue
Using the optional HP-UX feature Security Containment, you can set up a
virtual network interface for each secure compartment. A process in one
secure compartment can bind to a socket on a virtual network interface
associated with a different secure compartment. Although this process will
not be able to accept connections or use the socket to send or receive data, it
does prevent other processes from binding to that socket.
Workaround
Be sure your applications that access the network bind only to sockets on
the virtual network interface created for their respective secure
compartments.
For more information, see the Security Containment release notes and the
HP-UX 11i Security Containment Administrator’s Guide.