Skip Navigation Links | |
Exit Print View | |
![]() |
System Administration Guide: Oracle Solaris Zones, Oracle Solaris 10 Containers, and Resource Management Oracle Solaris 11 Express 11/10 |
Part I Oracle Solaris Resource Management
1. Introduction to Resource Management
2. Projects and Tasks (Overview)
3. Administering Projects and Tasks
4. Extended Accounting (Overview)
5. Administering Extended Accounting (Tasks)
6. Resource Controls (Overview)
7. Administering Resource Controls (Tasks)
8. Fair Share Scheduler (Overview)
9. Administering the Fair Share Scheduler (Tasks)
10. Physical Memory Control Using the Resource Capping Daemon (Overview)
11. Administering the Resource Capping Daemon (Tasks)
13. Creating and Administering Resource Pools (Tasks)
14. Resource Management Configuration Example
15. Introduction to Oracle Solaris Zones
16. Non-Global Zone Configuration (Overview)
17. Planning and Configuring Non-Global Zones (Tasks)
18. About Installing, Halting, Uninstalling, and Cloning Non-Global Zones (Overview)
19. Installing, Booting, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)
20. Non-Global Zone Login (Overview)
21. Logging In to Non-Global Zones (Tasks)
22. Moving and Migrating Non-Global Zones (Tasks)
23. About Packages on an Oracle Solaris 11 Express System With Zones Installed
24. Oracle Solaris Zones Administration (Overview)
25. Administering Oracle Solaris Zones (Tasks)
26. Troubleshooting Miscellaneous Oracle Solaris Zones Problems
Part III Oracle Solaris 10 Zones
27. Introduction to Oracle Solaris 10 Zones
28. Assessing an Oracle Solaris 10 System and Creating an Archive
30. Configuring the solaris10 Branded Zone
31. Installing the solaris10 Branded Zone
32. Booting a Zone and Zone Migration
33. solaris10 Branded Zone Login and Post-Installation Configuration
The zoneadm command described in Part II, Oracle Solaris Zones and 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 on the target system.
In addition to unpacking files from the archive, the install process performs checks, required postprocessing, and other functions to ensure that the zone is optimized to run on the host.
If you created an Oracle Solaris system archive from an existing system and use the -p (preserve sysidcfg) option when you install the zone, then the zone will have the same identity as the system used to create the image.
If you use the -u (sys-unconfig) option when you install the target zone, the zone produced will not have a hostname or name service configured.
![]() | Caution - You must use either the -p option or the -u option. If you do not specify one of these two options, an error results. |
|
The -a and -d options are mutually exclusive.
A configured solaris10 branded zone is installed by using the zoneadm command with the install subcommand.
For information about creating images of Oracle Solaris 10 systems, see Creating the Image for Directly Migrating Oracle Solaris 10 Systems Into Zones. To retain the sysidcfg identity from a system image that you created, without altering the image, use the -p option after the install subcommand. To remove the system identity from a system image that you created, without altering the image, use the -u option. The sys-unconfig occurs to the target zone.
The example procedure shows how to use the -a option with the created archive image of a physical installed Oracle Solaris 10 system.
You must be the global administrator or a user with the appropriate authorizations in the global zone to perform this procedure.
global# zoneadm -z s10-zone install -a /net/machine_name/s10-system.flar -u
You will see various messages as the installation completes. This can take some time.
global# zoneadm list -cv
ID NAME STATUS PATH BRAND IP 0 global running / ipkg shared - s10-zone configured /zones/s10-zone solaris10 shared
If the state is listed as configured, make the corrections specified in the message and try the zoneadm install command again.
If the state is listed as incomplete, first execute this command:
global# zoneadm -z my-zone uninstall
Then, make the corrections specified in the message and try the zoneadm install command again.
global# zoneadm list -iv
You will see a display that is similar to the following:
ID NAME STATUS PATH BRAND IP 0 global running / ipkg shared - s10-zone installed /zones/s10-zone solaris10 shared
Example 31-1 solaris10 Zone Installation
# zoneadm -z s10-zone install -u -a /net/machinename/s10_image.flar Log File: /var/tmp/s10-zone.install.21207.log Source: /net/machinename/s10_image.flar Installing: This may take several minutes... Postprocessing: This may take a minute... Result: Installation completed successfully. Log File: /zones/s10-zone/root/var/log/s10-zone.install.21207.log
If an installation fails, review the log file. On success, the log file is in /var/log inside the zone. On failure, the log file is in /var/tmp in the global zone.
If a zone installation is interrupted or fails, the zone is left in the incomplete state. Use the uninstall command with the -F option to reset the zone to the configured state.