Creating and Using Oracle Solaris Kernel Zones

Exit Print View

Updated: December 2014

Working With Kernel Zone Auxiliary States

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.

To view the global zone current state and the kernel zone auxiliary states, use the zoneadm list -s command.

global# zoneadm list -s
NAME             STATUS           AUXILIARY STATE
global          running
kzone1          running
kzone2          running
kzone3          running            debugging

The available kernel zone auxiliary states are as follows:


The zone has been suspended and will resume on the next boot. Note that the zone must be attached before this state is visible. A kernel zone appears in a suspended auxiliary state when undergoing a migration. See Migrating a Kernel Zone by Using Suspend and Resume.


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 4, About Non-Global Zone Login, in Creating and Using Oracle Solaris Zones .


The zone is in the running state but has panicked. The host is not affected. You must use zone console access to log in to a kernel zone in the panicked auxiliary state.

For information about zone states, see Chapter 1, Oracle Solaris Zones Introduction, in Introduction to Oracle Solaris Zones . For additional information about kernel zone auxiliary states, see the solaris-kz(5) man page. For information about the kernel debugger see the kmdb(1) man page.