HP-UX Virtual Partitions Administrator's Guide (includes A.03.04) (previously titled Installing and Managing HP-UX Virtual Partitions)

Monitor and Shell Commands
Commands: Displaying Monitor and Resource Information (vparstatus)
Chapter 5
142
Commands: Displaying Monitor and Resource Information
(vparstatus)
The Monitor and the partition database maintains information about all the virtual partitions, including the
current state of the virtual partitions and their resources. Using the shell command vparstatus, you can
display this information. This section describes the possible virtual partition states and the common usages of
the vparstatus command.
Virtual Partition States
Virtual partitions can be in the following states:
vparstatus output examples
The next few pages show examples of using the vparstatus command:
“vparstatus: summary information” on page 144
“vparstatus: verbose information” on page 145
“vparstatus: available resources” on page 147
“vparstatus: pending migrating CPUs operations” on page 152
“vparstatus: dual-core CPUs” on page 151
“vparstatus: CPU information on vPars A.04/A.05” on page 149
“vparstatus: pending migrating memory operations” on page 153
“vparstatus: pending nPartition RFR” on page 155
“vparstatus: Monitor and database information” on page 156
Table 5-2 Virtual Partition States
State Description
load The Monitor is loading the kernel image of the virtual partition. This is the first step of
booting a virtual partition. If successful, the state moves to boot.
boot The Monitor has successfully loaded the kernel image and is continuing with the boot
process. If the launch is successful, the state moves to up.
up The virtual partition is up and running.
shut The virtual partition is shutting down gracefully. Once the partition is shutdown, the
state moves to down.
down The virtual partition is down.
crash The virtual partition is crashing because of a panic (HPMC, TOC, etc.). Once the partition
has completed crashing, the state moves to down.
hung The virtual partition is not responding.
N/A The virtual partition is in a database file that is not active, so it has no state. The
database file can be inactive because either the system is in standalone mode (the vPars
Monitor is not running) or the database file acted upon is an alternate database file that is
not in Monitor memory.