|Skip Navigation Links|
|Exit Print View|
|System Administration Guide: Oracle Solaris 9 Containers Oracle Solaris Legacy Containers|
The solaris9 container uses the branded zones framework described in brands(5)to enable Solaris 9 binary applications to run unmodified on a machine with the latest Solaris Operating System kernel.
The solaris9 brand includes the tools necessary to install a Solaris 9 system image into a non-global zone. The brand supports the execution of 32-bit and 64-bit Solaris 9 applications on SPARC machines running the latest Solaris operating system.
The solaris9 brand supports the whole root non-global zone model. All of the required Solaris 9 software and any additional packages are installed into the private file systems of the zone.
The zonecfg(1M) utility is used to configure a solaris9 branded zone. Once a branded zone has been installed, that zone's brand cannot be changed or removed. The zoneadm(1M) utility is used to report the zone's brand type and administer the zone. The zlogin(1) utility is used to log in to the zone.
The solaris9 brand installer supports installing the zone from an image of an installed Solaris 9 system. This can be a full flash_archive(4), cpio(1) archive optionally compressed with gzip(1) or bzip2(1), or pax(1) xustar archive. The image can also be a level 0 ufsdump(1M), or a path to the top-level of a Solaris 9 system's root directory tree. The zone cannot be installed from standard Solaris 9 distribution media. The zoneadm(1M) brand-specific subcommands accept the following arguments:
Install the specified Solaris 9 system image into the zone. Either the -u or -p option is required and either the -a or -d option is required.
The path to the root directory of an installed Solaris 9 system.
Preserve the system configuration after installing the zone.
Run sys-unconfig(1M) on the zone after installing it.
Verbose output from the install process.
The solaris9 zone only supports user-level Solaris 9 applications. You cannot use Solaris 9 device drivers, Solaris 9 kernel modules, or Solaris 10 release file systems, such as zfs(1M) delegated datasets, from inside a solaris9 zone. However, you can add fs resources in zonecfg with type=zfs.
Native Solaris debugging tools such as DTrace (see dtrace(1M)) can be applied to Solaris 9 processes executing inside the zone, but the tools themselves must be running in the global zone.
During the process of installing the zone a "physical to virtual" conversion is automatically performed. After a solaris9 branded zone is migrated to a new host, this process should be repeated to ensure that the zone is optimized to run on the new host. The first time that the zone attempts to boot on the new host it will detect this situation and the zone will not boot until the following command is run: