| We've seen many examples of vPars in a variety of different boot states in Chapter 2 when we were creating and modifying vPars. When we boot a Virtual Partition, it progresses through load, then boot, and finally, up. There are other states in which you may find a Virtual Partition as well. Table 3-1 summarizes the states of Virtual Partitions at the time of this writing: Table 3-1. Virtual Partitions States| vPars State | Description |
|---|
| load | The kernel image of a Virtual Partition is being loaded into memory. This is done by the Virtual Partition monitor. | | boot | The Virtual Partition is in the process of booting. The kernel image has been successfully loaded by the Virtual Partition monitor. | | up | The Virtual Partition has been successfully booted and is running. | | shut | The Virtual Partition is in the process of shutting down. | | down | The Virtual Partition is not running and is down. | | crash | The Virtual Partition has experienced a panic and is crashing. | | hung | The Virtual Partition is not responding and is hung. |
We have seen several of these states in Chapter 2 when we created Virtual Partitions and watched them boot by issuing successive vparstatus commands. The following example shows the process of the Virtual Partition cable2 booting: # vparboot -p cable2 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================== ===== ========== ========================= ===== cable1 Up Dyn,Manl /stand/vmunix cable2 Load Dyn,Manl /stand/vmunix [Virtual Partition Resource CPU Num Memory (MB) Summary] CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== cable1 2/ 4 2 0 4 0/ 0 2048 cable2 2/ 2 2 0 4 0/ 0 1024 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================== ===== ========== ========================= ===== cable1 Up Dyn,Manl /stand/vmunix cable2 Boot Dyn,Manl /stand/vmunix [Virtual Partition Resource CPU Num Memory (MB) Summary] CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== cable1 2/ 4 2 0 4 0/ 0 2048 cable2 2/ 2 2 0 4 0/ 0 1024 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================== ===== ========== ========================= ===== cable1 Up Dyn,Manl /stand/vmunix cable2 Up Dyn,Manl /stand/vmunix [Virtual Partition Resource CPU Num Memory (MB) Summary] CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== cable1 2/ 4 2 0 4 0/ 0 2048 cable2 2/ 2 2 0 4 0/ 0 1024 # This example shows cable2 progressing through the load, then boot, and finally, up. cable2 was booted from cable1 running on the same hardware. The system had already gone through the boot process when cable1 booted. The boot time for cable2 is very quick since most of the hardware is already running. The boot time for the first Virtual Partition is comparable to the boot time of a non-Virtual Partition system, but the subsequent vPars boot much more quickly. | 
