A non-global zone can be in one of the following seven states:
The zone's configuration is complete and committed to stable storage. However, those elements of the zone's application environment that must be specified after initial boot are not yet present.
During an install or uninstall operation, zoneadm sets the state of the target zone to incomplete. Upon successful completion of the operation, the state is set to the correct state.
A damaged installed zone can be marked incomplete by using the mark subcommand of zoneadm. Zones in the incomplete state are shown in the output of zoneadm list –iv.
Indicates that the zone has been installed, but cannot be verified, made ready, booted, attached, or moved. A zone enters the unavailable state at the following times:
When the zone's storage is unavailable and svc:/system/zones:default begins, such as during system boot
When the zone's storage is unavailable
When archive-based installations fail after successful archive extraction
When the zone's software is incompatible with the global zone's software, such as after an improper –F (force) attach
The zone's configuration is instantiated on the system. The zoneadm command is used to verify that the configuration can be successfully used on the designated Oracle Solaris system. Packages are installed under the zone's root path. In this state, the zone has no associated virtual platform.
The virtual platform for the zone is established. The kernel creates the zsched process, network interfaces are set up and made available to the zone, file systems are mounted, and devices are configured. A unique zone ID is assigned by the system. At this stage, no processes associated with the zone have been started.
User processes associated with the zone application environment are running. The zone enters the running state as soon as the first user process associated with the application environment (init) is created.
These states are transitional states that are visible while the zone is being halted. However, a zone that is unable to shut down for any reason will stop in one of these states.
Chapter 3, Installing, Booting, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones, in Creating and Using Oracle Solaris Zones and the zoneadm (1M) man page describe how to use the zoneadm command to initiate transitions between these states.
In addition, Oracle Solaris Kernel Zones have three auxiliary states, which are used to notify the host with additional information about the current zone state.
Primary state is halted, with an auxiliary state of suspended.
The zone is running, but the zone cannot respond to external events, such as networking. zlogin checks for this state and waits until the state is cleared before starting a zlogin session.
The zone has panicked, but the zone cannot respond to external events until it is rebooted.
For additional information, see Creating and Using Oracle Solaris Kernel Zones and the solaris-kz (5) man page.
|