HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

NOTE: On a vPars system, when a virtual partition goes down and contains a deconfigured
or deactivated CPU, the Monitor will try to decommission the CPU from use and replace it with
another good CPU if possible. If this is not possible, the Monitor will not allow the partition to
boot until the deconfigured or deactivated CPU can be taken out of use. Following are some
cases where the Monitor may not allow the virtual partition to boot:
• There is a deconfigured or deactivated CPU which has been reserved for the partition as
part of the total (cpu::num) request and Monitor does not have any free CPUs with which
to replace it. To correct this, you can delete CPUs from other partitions or from this partition.
• There is a deconfigured or deactivated CPU that has been bound to the partition by hardware
path (cpu:hw_path) which the Monitor is not able to replace with another available CPU.
To correct this, you can remove the CPU specified by hardware path using -d cpu:hw_path
to allow the deconfigured or deactivated CPU to be decommissioned and replaced with
another (working) CPU.
• There is a deconfigured CPU which has been reserved for the partition as part of a CLP
request (cell:cell_ID:cpu::num) and there are no free CLPs in that cell. To correct this, you
can make available CPUs from that cell by deleting the CPUs that are part of this cell from
other partitions or delete the CPUs from the cell in this partition.
Dual-core processors have two CPUs (that is, cores) per processor. Deactivation happens on a
CPU level, but deconfiguration happens at the socket level. If a processor’s socket is deconfigured,
both CPUs sharing the socket will be unavailable.
(Integrity only) If a CPU is marked for deconfiguration using an EFI command and the nPartition
is not rebooted (for example, the vPars Monitor is immediately booted), the vPars Monitor will
not know or indicate (including with vparstatus) that the CPU has been marked for
deconfiguration and will use the CPU like any other working CPU.
Memory, CPU: Canceling Pending Operations
Beginning with vPars A.05.01, you can now cancel pending CPU and memory operations with
the new -C SequenceID option to the vparmodify command:
# vparmodify -p vp_name -C sequenceID
The sequenceID value comes from the vparstatus -v output.
CPU and memory operations may not occur instantaneously. Therefore, it is possible that you
may want to cancel a pending (in other words, still in progress) operation. If a virtual partition
has a pending CPU or memory operation, the letter p will be displayed in the summary output
and the words (Migration pending) will be displayed in Status: field of the vparstatus
output.
In a mixed HP-UX 11i v2/v3 vPars environment, the virtual partitions running vPars A.04.xx do
not support sequence IDs. If you execute vparstatus -von a vPars A.05.01 partition to get
information about a vPars A.04.xx partition, the SequenceID will be N/A. In addition, you
cannot cancel a pending operation on a vPars A.04.xx partition.
Status: Pending
An operation can only be canceled when vparstatus shows a Status value of PENDING and
a SequenceID.
keira1# vparstatus -p keira2 -v
...
[Resource OL* Details]
Sequence ID: 1234
Operation: Memory Addition
Status: PENDING
The following are the valid values for the Status: field of the vparstatus output:
Memory, CPU: Canceling Pending Operations 205