Kernel zones use auxiliary states to communicate supplementary state information to the global zone. A kernel zone does not have an auxiliary state set by default. Auxiliary states are set only when you initiate debugging and kernel maintenance operations or migrate zones.
The kernel zone auxiliary states are as follows:
The kernel zone is in the kernel debugger, kmdb. Although the zone is in the running state, the zone cannot service any network requests. You must connect to the zone console to interact with kmdb. For information about how to connect to the zone console, see Chapter 2, Setting Up a Non-Global Zone in Creating and Using Oracle Solaris Zones.
The zone is booted on the system, and is receiving the live migration image. It is not yet fully running until live migration is complete.
The zone is fully running, but is being live migrated to another system.
The zone is known to the system, but its configuration is missing. State of the zone is always incomplete.
The zone is in the running state but has panicked. The host system is not affected. You must use zone console access to log in to a kernel zone in the panicked auxiliary state.
The zone has been suspended and will resume on the next boot. The zone must be attached before this state is visible. A kernel zone appears in the suspended auxiliary state before undergoing a warm migration. See Migrating an Oracle Solaris Kernel Zone.
To view the global zone current state and the kernel zone auxiliary states, use the zoneadm list -s command. Output is similar to the following:
global$ zoneadm list -s NAME STATUS AUXILIARY STATE global running kzone1 running kzone2 running kzone3 running debugging
For additional information about kernel zone auxiliary states, see the solaris-kz(7) man page.
For information about non-global zone states, see Chapter 1, Oracle Solaris Zones Introduction in Introduction to Oracle Solaris Zones.
For information about the kernel debugger see the kmdb(1) man page.