HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)
For additional information on using iCAP (formerly known as iCOD), including temporary-iCAP
CPUs with vPars, see “CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04.xx
and iCAP B.07)” (page 225).
NOTE:
Using vPars A.03.xx and Earlier Syntax on a vPars A.04.xx System
Although not recommended under most circumstances, you can still use the vPars A.03.xx CPU
syntax on vPars A.04.xx systems. However, the concepts and rules of boot processors and dynamic
CPUs in A.04.xx will apply because the concepts and rules of bound and unbound CPUs in A.03.xx
no longer apply.
For more information, see “CPU: Syntax, Rules, and Notes” (page 224).
CPU: Boot Processor and Dynamic CPU Definitions
Beginning with vPars A.04.01, the restrictions of bound CPUs have been removed as well as the
terms bound and unbound. Now, there are two types of CPUs: boot processors and dynamic CPUs.
The Boot Processor is the CPU on which the OS kernel of the virtual partition was booted. There
is one boot processor per virtual partition. On booting of a virtual partition, the vPars Monitor
determines which CPU becomes the boot processor. Note that the specific CPU chosen as the boot
processor may differ across virtual partition reboots.
Dynamic CPUs are all the other CPUs, because all CPUs, except the boot processor of each virtual
partition, can be dynamically migrated. You can find which CPU is the boot processor by using
the vparstatus command; see “Commands: Displaying vPars Monitor and Resource Information
(vparstatus)” (page 140).
Note that you can only add CPUs that are available. If you are using iCAP (formerly known as
iCOD), the CPUs must be active and authorized by iCAP before you can add it to a virtual partition.
In A.04.xx, all CPUs can process I/O interrupts. See “Managing I/O Interrupts” (page 225).
CPU: Specifying Min and Max Limits
The syntax to specify min and max CPUs assigned to a virtual partition is:
-[a|m] cpu:::[min][:max]
where:
-a is adding (used with vparcreate or vparmodify)
-m is modifying (used with vparmodify)
min is the minimum number of CPUs for the virtual partition to boot and the minimum number
of CPUs that must remain assigned to the partition
max is the maximum number of CPUs that can be assigned to the virtual partition
NOTE: The virtual partition must be in the down state to set the min or max value.
The total count of CPUs in the virtual partition must always be greater than or equal to min and
less than or equal to max.
See “CPU: Syntax, Rules, and Notes” (page 224) regarding the new concepts and count rules for
min.
220 CPU, Memory, and I/O Resources (A.04.xx)