JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


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)

12.  Resource Pools (Overview)

13.  Creating and Administering Resource Pools (Tasks)

14.  Resource Management Configuration Example

Part II Oracle Solaris Zones

15.  Introduction to Oracle Solaris Zones

16.  Non-Global Zone Configuration (Overview)

17.  Planning and Configuring Non-Global Zones (Tasks)

18.  About Installing, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones (Overview)

19.  Installing, Booting, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)

20.  Non-Global Zone Login (Overview)

21.  Logging In to Non-Global Zones (Tasks)

22.  About Zone Migrations and the zonep2vchk Tool

23.  Migrating Oracle Solaris Systems and Migrating Non-Global Zones (Tasks)

24.  About Automatic Installation and Packages on an Oracle Solaris 11.1 System With Zones Installed

Image Packaging System Software on Systems Running the Oracle Solaris 11.1 Release

Zones Packaging Overview

About Packages and Zones

About Adding Packages in Systems With Zones Installed

Using pkg in the Global Zone

Using the pkg install Command in a Non-Global Zone

Adding Additional Packages in a Zone by Using a Custom AI Manifest

About Removing Packages in Zones

Package Information Query

Proxy Configuration on a System That Has Installed Zones

Configuring the Proxy in the Global Zone

Overriding system-repository Proxies by Using https_proxy and http_proxy

Parallel Zone Updates

How Zone State Affects Package Operations

25.  Oracle Solaris Zones Administration (Overview)

26.  Administering Oracle Solaris Zones (Tasks)

27.  Configuring and Administering Immutable Zones

28.  Troubleshooting Miscellaneous Oracle Solaris Zones Problems

Part III Oracle Solaris 10 Zones

29.  Introduction to Oracle Solaris 10 Zones

30.  Assessing an Oracle Solaris 10 System and Creating an Archive

31.  (Optional) Migrating an Oracle Solaris 10 native Non-Global Zone Into an Oracle Solaris 10 Zone

32.  Configuring the solaris10 Branded Zone

33.  Installing the solaris10 Branded Zone

34.  Booting a Zone, Logging in, and Zone Migration



How Zone State Affects Package Operations

The following table describes what will happen when packaging commands are used on a system with non-global zones in various states.

Zone State
Effect on Package Operations
Package tools can be run. No software has been installed yet.
If zoneadm is operating on the zone, package tools should not be used. If no zoneadm process is operating on the zone, package operations are safe to run, but no software in this zone will be changed and any software in the zone will not affect dependency resolution.
The software image within the zone is not accessible. The software image will not be changed, nor will it affect dependency resolution.
Package tools can be run.

Note that immediately after zoneadm -z zonename install has completed, the zone is also moved to the installed state.

Package tools can be run.
Package tools can be run.

A non-global zone transitions to the unavailable state when the storage for the zone is not accessible or when the image of the zone, which is described in pkg(5), is out of sync with the global zone's image. This state transition occurs to prevent a problem that is affecting a non-global zone from blocking package operations in the global zone.

When a zone's storage is temporarily unavailable and package operations that change the version of installed software occur, it is likely that after fixing the storage problem, the zone might need to be attached by using one of the solaris brand's attach options that allow for updates. For example, zoneadm -z zonename attach -u might be required to synchronize versions of critical software between the global zone and a non-global zone that is in the unavailable state.