Previous
How to Mark an Installed Non-Global Zone Incomplete
If administrative changes on the system have rendered a zone unusable or inconsistent, it is possible to change the state of an installed zone to incomplete.
You must be the global administrator in the global zone to perform this procedure.
Become superuser, or assume the Primary Administrator role.
To create the role and assign the role to a user, see "Using the Solaris Management Tools With RBAC (Task Map)" in System Administration Guide: Basic Administration.
Mark the zone testzone incomplete.
global# zoneadm -z testzone mark incomplete
Use the list subcommand with the -i and -v options to verify the status.
global# zoneadm list -iv
You will see a display that is similar to the following:
ID NAME STATUS PATH BRAND 0 global running / native - my-zone installed /export/home/my-zone native - testzone incomplete /export/home/testzone native
More Information
Marking a Zone Incomplete
The -R root option can be used with the mark and list subcommands of zoneadm to specify an alternate boot environment. See zoneadm(1M) for more information.
Note - Marking a zone incomplete is irreversible. The only action that can be taken on a zone marked incomplete is to uninstall the zone and return it to the configured state. See How to Uninstall a Zone.
(Optional) How to Transition the Installed
Zone to the Ready State
Transitioning into the ready state prepares the virtual platform to begin running user processes. Zones in the ready state do not have any user processes executing in them.
You can skip this procedure if you want to boot the zone and use it immediately. The transition through the ready state is performed automatically when you boot the zone.
You must be the global administrator in the global zone to perform this procedure.
Become superuser, or assume the Primary Administrator role.
To create the role and assign the role to a user, see "Using the Solaris Management Tools With RBAC (Task Map)" in System Administration Guide: Basic Administration.
Use the zoneadm command with the -z option, the name of the zone, which is my-zone, and the ready subcommand to transition the zone to the ready state.
global# zoneadm -z my-zone ready
At the prompt, use the zoneadm list command with the -v option to verify the status.
global# zoneadm list -v
You will see a display that is similar to the following:
ID NAME STATUS PATH BRAND 0 global running / native 1 my-zone ready /export/home/my-zone native
Note that the unique zone ID 1 has been assigned by the system.
How to Boot a Zone
Booting a zone places the zone in the running state. A zone can be booted from the ready state or from the installed state. A zone in the installed state that is booted transparently transitions through the ready state to the running state. Zone login is allowed for zones in the running state.
Tip - Note that you perform the internal zone configuration when you initially log in to the zone. This is described in Performing the Initial Internal Zone Configuration.
If you plan to use an /etc/sysidcfg file to perform initial zone configuration, as described in How to Use an /etc/sysidcfg File to Perform the Initial Zone Configuration, create the sysidcfg file and place it the zone's /etc directory before you boot the zone.
You must be the global administrator in the global zone to perform this procedure.
Become superuser, or assume the Primary Administrator role.
To create the role and assign the role to a user, see "Using the Solaris Management Tools With RBAC (Task Map)" in System Administration Guide: Basic Administration.
Use the zoneadm command with the -z option, the name of the zone, which is my-zone, and the boot subcommand to boot the zone.
global# zoneadm -z my-zone boot
When the boot completes, use the list subcommand with the -v option to verify the status.
global# zoneadm list -v
You will see a display that is similar to the following:
ID NAME STATUS PATH BRAND 0 global running / native 1 my-zone running /export/home/my-zone native
Example 20-2 Specifying Boot Arguments for Zones
Boot a zone using the -m verbose option:
global# zoneadm -z my-zone boot -- -m verbose |
Reboot a zone using the -m verbose boot option:
global# zoneadm -z my-zone reboot -- -m verbose |
Zone administrator reboot of the zone my-zone, using the -m verbose option:
my-zone# reboot -- -m verbose |
Troubleshooting
If a message indicating that the system was unable to find the netmask to be used for the IP address specified in the zone's configuration displays, see netmasks Warning Displayed When Booting Zone. Note that the message is only a warning and the command has succeeded.
How to Boot a Zone in Single-User Mode
You must be the global administrator in the global zone to perform this procedure.
Become superuser, or assume the Primary Administrator role.
To create the role and assign the role to a user, see "Using the Solaris Management Tools With RBAC (Task Map)" in System Administration Guide: Basic Administration.
Boot the zone in single-user mode.
global# zoneadm -z my-zone boot -- -s
Where to Go From Here
To log in to the zone and perform the initial internal configuration, see Chapter 21, Non-Global Zone Login (Overview) and Chapter 22, Logging In to Non-Global Zones (Tasks).
Halting, Rebooting, Uninstalling, Cloning, and Deleting Non-Global Zones (Task Map)
Task | Description | For Instructions |
|---|---|---|
Halt a zone. | The halt procedure is used to remove both the application environment and the virtual platform for a zone. The procedure returns a zone in the ready state to the installed state. To cleanly shut down a zone, see How to Use zlogin to Shut Down a Zone. | |
Reboot a zone. | The reboot procedure halts the zone and then boots it again. | |
Uninstall a zone. | This procedure removes all of the files in the zone's root file system. Use this procedure with caution. The action is irreversible. | |
Provision a new non-global zone based on the configuration of an existing zone on the same system. | Cloning a zone is an alternate, faster method of installing a zone. You must still configure the new zone before you can install it. | |
Delete a non-global zone from the system. | This procedure completely removes a zone from a system. |
Halting, Rebooting, and Uninstalling Zones
How to Halt a Zone
The halt procedure is used to remove both the application environment and the virtual platform for a zone. To cleanly shut down a zone, see How to Use zlogin to Shut Down a Zone.
You must be the global administrator in the global zone to perform this procedure.
Become superuser, or assume the Primary Administrator role.
To create the role and assign the role to a user, see "Using the Solaris Management Tools With RBAC (Task Map)" in System Administration Guide: Basic Administration.
List the zones running on the system.
global# zoneadm list -v
You will see a display that is similar to the following:
ID NAME STATUS PATH BRAND 0 global running / native 1 my-zone running /export/home/my-zone native
Use the zoneadm command with the -z option, the name of the zone, for example, my-zone, and the halt subcommand to halt the given zone.
global# zoneadm -z my-zone halt
List the zones on the system again, to verify that my-zone has been halted.
global# zoneadm list -iv
You will see a display that is similar to the following:
ID NAME STATUS PATH BRAND 0 global running / native - my-zone installed /export/home/my-zone native
Boot the zone if you want to restart it.
global# zoneadm -z my-zone boot
Troubleshooting
If the zone does not halt properly, see Zone Does Not Halt for troubleshooting tips.