HP-UX vPars and Integrity VM V6.3 Administrator Guide

5.2 Configuring CPU resources for vPars
The CPU resource configured for vPar is the physical CPU on the VSP. The physical CPUs allotted
to a vPar are dedicated to that vPar alone and are not shared with either the VSP or any other
vPar or VM guest running on the VSP. Hence, the concept of entitlement does not apply to vPar
cores. You can specify a maximum of (total VSP cores –1) for a single vPar.
The following example shows a VSP with 16 cores, of which 4 CPUs are reserved for 4 1-CPU
vPars.
# hpvmstatus
[Virtual Machines]
Virtual Machine VM # Type OS Type State #VCPUs #Devs #Nets Memory
Name
=============== ==== ==== ======= ======= ====== ===== ===== =======
VPAR4 4 VP HPUX Off 1 1 1 2048 MB
GUEST5 5 SH HPUX Off 1 1 1 2 GB
GUEST7 7 SH HPUX Off 1 1 1 2 GB
VPAR3 3 VP HPUX Off 1 1 1 2048 MB
VPAR1 1 VP HPUX Off 1 1 1 2048 MB
VPAR2 2 VP HPUX Off 1 1 1 2048 MB
GUEST6 6 SH HPUX Off 1 1 1 2 GB
# hpvmstatus -s
[HPVM Server System Resources]
…
Total number of operable system cores = 16
CPU cores allocated for VSP = 1
CPU cores allocated for vPars and VMs = 15
CPU cores currently in use or reserved for later use = 4
…
Available CPU cores for a virtual partition = 11
…
# vparstatus -A
[Available CPUs]: 11
…
The mpsched command on the VSP shows that 16 CPUs are still available as all vPars are currently
DOWN.
# mpsched -s
System Configuration
=====================
Locality Domain Count: 4
Processor Count : 16
Domain Processors
------ ----------
0 0 2 4 6
1 8 10 12 14
2 16 18 20 22
3 24 26 28 30
# hpvmstart -p 1
…
hpvmstart: Successful start initiation of vPar or VM 'VPAR1'
Now that the vPar is started, one core (ID: 22) from the VSP is dedicated to running the vPar
‘VPAR1’. This can be confirmed by the absence of one VSP core in the mpsched command output.
# mpsched -s
5.2 Configuring CPU resources for vPars 55