This chapter discusses the following topics:
Installing an lx zone on your system
Cloning a zone on your system
Halting, rebooting, and uninstalling zones
The zoneadm command described in the zoneadm(1M) man page is the primary tool used to install and administer non-global zones. Operations using the zoneadm command must be run from the global zone. The following tasks can be performed using the zoneadm command:
Verify a zone
Install a zone
Boot a zone
Display information about a running zone
Halt a zone
Reboot a zone
Uninstall a zone
Relocate a zone from one point on a system to another point on the same system
Provision a new zone based on the configuration of an existing zone on the same system
Migrate a zone, used with the zonecfg command
For zone installation and verification procedures, see Chapter 33, Installing, Booting, Halting, Uninstalling and Cloning lx Branded Zones (Tasks) and the zoneadm(1M) man page. Also refer to the zoneadm(1M) man page for supported options to the zoneadm list command. For zone configuration procedures, see Chapter 31, Configuring the lx Branded Zone (Tasks), and the zonecfg(1M) man page. Zone states are described in Non-Global Zone State Model.
If you plan to produce Solaris auditing records for zones, read Using Solaris Auditing in Zones before you install non-global zones.
Once the zone is installed, all software configuration and management has to be done by the zone administrator using Linux tools from inside the zone.
You can install an lx branded zone by using a tarball, CD-ROM or DVD discs, or an ISO image. If you install from discs or from an ISO image, you can specify Sun package cluster categories. The categories are cumulative. If you do not specify a cluster, the default is desktop.Table 32–1 Package Cluster Categories
The minimum set of packages needed to construct a zone.
core plus server-oriented packages, such as httpd, mailman, imapd, and spam-assassin.
server plus user-oriented packages, such as evolution, gimp, mozilla, and openoffice
desktop plus developer packages, such as bison, emacs, gcc, vim-X11, and many library development packages
Everything on the install media that is known not to interfere with the zone's operation. Certain packages might not function in a Linux zone.
To install configured lx branded zones, see How to Install an lx Branded Zone.
This section applies to only to initial zone construction, and not to the cloning of existing zones.
After you have configured a non-global zone, you should verify that the zone can be installed safely on your system's configuration. You can then install the zone. The files needed for the zone's root file system are installed by the system under the zone's root path. The Linux zone will be populated from CD, ISO images, or a tarball, as described in How to Install an lx Branded Zone.
The resources specified in the configuration file are added when the zone transitions from installed to ready. A unique zone ID is assigned by the system. File systems are mounted, network interfaces are set up, and devices are configured. Transitioning into the ready state prepares the virtual platform to begin running user processes.
A zone in the ready state does not have any user processes executing in it. The primary difference between a ready zone and a running zone is that at least one process is executing in a running zone. See the init(1M) man page for more information.
In the ready state, the zsched and zoneadmd processes are started to manage the virtual platform.
The zones administration daemon, zoneadmd, is the primary process for managing the zone's virtual platform. For more information, see The zoneadmd Daemon.
The process that manages the application environment, zsched, is described in The zsched Zone Scheduler.
The zoneadm command is used to create the zone application environment.
All additional configuration is done by the zone administrator using Linux tools from within the zone.
Note that the root (superuser) password will be root when the zone is installed from the Sun tarball. The root (superuser) password will be unset (blank) when the zone is installed from ISO images or a CD.
This section provides an overview of the procedures for halting, rebooting, uninstalling, and cloning zones.
The zoneadm halt command is used to remove both the application environment and the virtual platform for a zone. The zone is then brought back to the installed state. All processes are killed, devices are unconfigured, network interfaces are destroyed, file systems are unmounted, and the kernel data structures are destroyed.
The halt command does not run any shutdown scripts within the zone. To shut down a zone, see How to Use zlogin to Shut Down a Zone.
If the halt operation fails, see Zone Does Not Halt.
Zones support the following boot arguments used with the zoneadm boot and reboot commands:
The following definitions apply:
Selects an alternative executable to be the first process. altinit must be a valid path to an executable. The default first process is described in init(1M).
Boots the zone to init level s.
For usage examples, see How to Boot an lx Branded Zone and How to Boot an lx Branded Zone in Single-User Mode.
For information on the init command, see init(1M).
If you set the autoboot resource property in a zone's configuration to true, that zone is automatically booted when the global zone is booted. The default setting is false.
Note that for zones to autoboot, the zones service svc:/system/zones:default must also be enabled.
The zoneadm uninstall command removes all of the files under the zone's root file system. Before proceeding, the command prompts you to confirm the action, unless the -F (force) option is also used. Use the uninstall command with caution, because the action is irreversible.
Cloning allows you to copy an existing configured and installed zone on your system to rapidly provision a new zone on the same system. For more information about the clone process, see About Cloning Non-Global Zones. To clone an lx branded zone, see Cloning an lx Branded Zone on the Same System.