Commands: Displaying vPars Monitor and Resource Information (vparstatus)

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:

	NOTE: Actual vparstatus output differs from version to version of vPars. Depending on your version and system, the output shown below may differ. For detailed usage, syntax, and information, see the manpage vparstatus(1M) on your vPars system. The kernel path shown in the vparstatus output is the kernel path set in the vPars database. This may differ from the actual kernel in use.

vparstatus: Summary Information

Use vparstatus with no options.

Examples

vparstatus: Verbose Information

Use vparstatuswith verbose (-v) option.

Examples

vparstatus: Available Resources

Use vparstatuswith available resources (-A) option. This shows the resources not assigned to any virtual partitions.

Examples

vparstatus: CPU Information on vPars A.04/A.05

While a virtual partition is in the down state, no specific CPU is assigned to the virtual partition as the boot processor but one is allocated by the vPars Monitor if needed (there are no CPUs assigned to the virtual partition). The boot processor is determined when the virtual partition is booted.

Note that the output does not determine which commands were issued; different commands can be used to arrive at the same vparstatus output.

Example

Table 5-3 possible commands to arrive at vparstatus output

vparstatus output (final)

set of possible commands in sequence to create vparstatus output

keira1 # vparstatus -p keira1 -v [Virtual Partition Details] Name: keira1 State: Up Attributes: Dynamic,Autoboot,Autosearch Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 1/12 User assigned [Path]: 1.10 Boot processor [Path]: 1.12 Monitor assigned [Path]: 0.10 0.11 1.11 Non-cell-specific: User assigned [Count]: 2 Monitor assigned [Count]: 2 Cell-specific [Count]: Cell ID/Count 1 1 ...

# vparcreate -p keira1 -a cpu:::1:12 -a cpu::4 (min==1, max==12, total==4 4 non-CLPs are reserved by the Monitor) # vparmodify -p keira1 -a cpu:1/10 -a cpu:1/12 (since the vpar is down, total is not modified. therefore, 2 of the 4 CPUs assigned by the Monitor become user-assigned by hardware_path (1.10 and 1.12). total==4 (2 assigned by hardware path and 2 assigned by Monitor)) # vparmodify -p keira1 -a cell:1:cpu::1 (since the specification is by CLP, total is modified. the Monitor chooses which CPU from cell 1. totat==5 (2 assigned by hardware path and 2 assigned by Monitor and 1 assigned by CLP)) # vparboot -p keira1 assume I/O and memory have been assigned so that keira1 can boot. at boot time: min==1, max==12 user-assigned CPU is 1.10 boot processor is chosen by Monitor to be the other user-assigned CPU at 1.12 2 CPUs assigned by Monitor are 0.10 and 0.11 1 CPU assigned by the Monitor by CLP is 1.11

Table 5-4 possible commands to arrive at vparstatus output

vparstatus output (final)

another set of possible commands in sequence to create vparstatus output

keira1 # vparstatus -p keira1 -v [Virtual Partition Details] Name: keira1 State: Up Attributes: Dynamic,Autoboot,Autosearch Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 1/12 User assigned [Path]: 1.10 Boot processor [Path]: 1.12 Monitor assigned [Path]: 0.10 0.11 1.11 Non-cell-specific: User assigned [Count]: 2 Monitor assigned [Count]: 2 Cell-specific [Count]: Cell ID/Count 1 1 ...

# vparcreate -p keira1 -a cpu:1.12 (total==1) # vparboot -p keira1 (assume I/O and memory have been assigned so that keira1 can boot. at this point the cpu assigned by hw_path (1.12) is the only CPU, so it becomes the boot processor. Note that 1.12 is only listed once; it is not listed under both “Boot Processor” and “User Assigned”) # vparmodify -p keira1 -a cpu:1.10 (1.10 is added and listed as “user assigned”) # vparmodify -p keira1 -a cpu::2 (0.10 and 0.11 are chosen by the Monitor and added) # vparmodify -p keira1 -a cell:1:cpu::1 (1.11 is added and listed under “Cell-specific”)

vparstatus: Dual-Core CPUs

You can see the sibling and virtual partition assignment using vparstatus-d. If you do not have a dual-core system, the output will show dashes (-) for the sibling and assignment information.

Example  

When you do have dual-core system, the vparstatus -d output will look similar to the following:

vparstatus: Pending Migrating CPUs Operations

Migrating CPUs may not occur instantaneously. If a virtual partition has a pending (in other words, still in progress) addition or deletion of one or more CPUs, the letter p will be displayed next to the number of CPUs in the summary output and the words (migration pending) will be displayed in the detailed output:

Example

For more information on canceling pending memory or CPU operations, see “Memory, CPU: Canceling Pending Operations”.

vparstatus: Pending Migrating Memory Operations

Migrating memory may not occur instantaneously. If a virtual partition has a pending (in other words, still in progress) addition or deletion of memory, the letter p will be displayed next to the total ILM in the summary output and the words (Migration pending) will be displayed in the detailed output:

Example

For more information on canceling pending memory or CPU operations, see “Memory, CPU: Canceling Pending Operations”.

vparstatus: Base and Float Memory Amounts

With vPars A.05.xx, you can assign ILM and/or CLM memory as either base or float. The verbose (-v) output of vparstatus shows how much is float relative to the total ILM and CLM memory that is assigned.

For more information on base and float memory, see “Memory: Concepts and Functionality”.

vparstatus: Pending nPartition Reboot for Reconfiguration

On an nPartitionable system, if the nPartition has a pending Reboot for Reconfiguration, the vparstatus output will show the following message:

Example:  

keira1# vparstatus
[Virtual Partition]
                                                                          Boot
Virtual Partition Name         State Attributes Kernel Path               Opts
============================== ===== ========== ========================= =====
keira1                         Up    Dyn,Auto   /stand/vmunix
keira2                         Down  Dyn,Manl   /stand/vmunix             boot

[Virtual Partition Resource Summary]
                                           CPU    Num        Memory (MB)
                                  CPU     Bound/   IO   # Ranges/
Virtual Partition Name          Min/Max  Unbound  devs  Total MB    Total MB
==============================  ================  ====  ====================
keira1                           2/  8    2   0     7    0/  0         2048
keira2                           2/ 12    2   2     3    0/  0         2048

Note:  A profile change is pending.  The hard partition must be rebooted to complete it.

vparstatus: vPars Monitor and Database Information

Beginning with vPars A.03.02, the -m option displays the console path, the hardware path from which the vPars Monitor was booted, the fleshiest path of the vPars Monitor, and the vPars database file that is being used by the vPars Monitor. Beginning with vPars A.04.01, memory ranges used by the vPars Monitor and firmware are also displayed.

Examples