Technical data

Virtual Partitions (vPars) Management on nPartitions
Configuring vPar Autoboot
HP System Partitions Guide: Administration for nPartitions, rev 5.1
499
Next the user issues the vparstatus command to list the current
settings for the vPars defined in the /stand/vpdb file. Because the
vparstatus command is issued when the local nPartition is booted in
non-vPars mode, the command lists info based on the vpdb file rather
than the vPars monitor (which is not running).
# vparstatus
vparstatus: Warning: Virtual partition monitor not running, Requested resources
shown.
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ========== ========================= =====
Shad N/A Dyn,Manl /stand/vmunix
Mesh N/A Dyn,Manl /stand/vmunix
[Virtual Partition Resource Summary]
CPU Num Memory (MB)
CPU Bound/ IO # Ranges/
Virtual Partition Name Min/Max Unbound devs Total MB Total MB
============================== ================ ==== ====================
Shad 2/ 3 2 0 6 0/ 0 2048
Mesh 1/ 2 1 1 6 0/ 0 1024
#
In this example both vPars, named “Shad” and “Mesh”, originally are
configured to be booted manually, as shown in the previous vparstatus
command output: the boot attribute for each is listed as “Manl” (manual).
Next the vparmodify command reconfigures the boot attribute for the
vPar named “Mesh” to auto.
After changing the boot attribute, issuing the vparstatus command
shows updated info about “Mesh” and lists its boot attribute as “Auto”
(auto).
# vparmodify -p Mesh -B auto
# vparstatus -p Mesh
vparstatus: Warning: Virtual partition monitor not running, Requested resources
shown.
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ========== ========================= =====
Mesh N/A Dyn,Auto /stand/vmunix
[Virtual Partition Resource Summary]
CPU Num Memory (MB)
CPU Bound/ IO # Ranges/
Virtual Partition Name Min/Max Unbound devs Total MB Total MB