|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|
The solaris10 branded zone, described in the solaris10(5) man page, is a complete runtime environment for Oracle Solaris 10 applications on SPARC and x86 machines running the Oracle Solaris 10 10/09 operating system or later released update. If you are running an Oracle Solaris 10 release earlier than Oracle Solaris 10 10/09, it is possible to use the earlier update release if you first install the kernel patch 141444-09 (SPARC) or 141445-09 (x86/x64), or later version, on the original system. You must install the patch before you create the archive that will be used to install the zone. It is the kernel patch of the release that is the prerequisite for migration to an Oracle Solaris 10 Container, not the full Oracle Solaris 10 10/09 release. For information regarding patches, contact your support provider.
The brand is supported on all sun4v, sun4u, and x86 architecture machines that the Oracle Solaris 11 Express release has defined as supported platforms. The brand supports the execution of 32-bit and 64-bit Oracle Solaris 10 applications.
The brand includes the tools required to install an Oracle Solaris 10 system image into a non-global zone. You cannot install a solaris10 branded zone directly from Oracle Solaris 10 media. A physical-to-virtual (P2V) capability is used to directly migrate an existing system into a non-global zone on a target system. The brand also supports the tools used to migrate an Oracle Solaris 10 native zone into a solaris10 brand non-global zone. The virtual-to-virtual (V2V) process for migrating an Oracle Solaris 10 native non-global zone into a solaris10 branded zone supports the same archive formats as P2V. See Chapter 29, (Optional) Migrating an Oracle Solaris 10 native Non-Global Zone Into an Oracle Solaris 10 Container for more information.
The solaris10 brand supports the whole root non-global zone model. All of the required Oracle Solaris 10 software and any additional packages are installed into the private file systems of the zone.
The non-global zone must reside on its own ZFS dataset; only ZFS is supported. The ZFS dataset will be created automatically when the zone is installed or attached. If a ZFS dataset cannot be created, the zone will not install or attach. Note that the parent directory of the zone path must also be a ZFS dataset, or the file system creation will fail.
Any application or program that executes in a native Oracle Solaris 10 non-global zone should also work in a solaris10 branded zone.
Note - You can create and install solaris10 branded zones on an Oracle Solaris Trusted Extensions system that has labels enabled, but you can only boot branded zones on this system configuration if the brand being booted is the labeled brand. Customers using Oracle Solaris Trusted Extensions on Oracle Solaris 10 systems must transition to a certified Oracle Solaris system configuration.