| Skip Navigation Links | |
| Exit Print View | |
|
man pages section 5: Standards, Environments, and Macros Oracle Solaris 11.1 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
man pages section 5: Standards, Environments, and Macros Oracle Solaris 11.1 Information Library |
- Solaris 10 branded zone
The solaris10 brand uses the branded zones framework described in brands(5) to enable Solaris 10 binary applications to run unmodified on a machine with the latest Solaris Operating System kernel.
Oracle Solaris 10 Zones are solaris10 branded zones that host x86 and SPARC Solaris 10 9/10 (or later released Oracle Solaris 10 update) user environments running on the Oracle Solaris 11 kernel.
Note that it is possible to use an earlier Oracle Solaris 10 release if you first install the kernel patch 142909-17 (SPARC) or 142910-17 (x86/x64), or later version, on the original system.
The solaris10 brand includes the tools necessary to install a Solaris 10 system image into a non-global zone. It also supports the tools necessary to migrate a Solaris 10 native zone to a solaris10 branded zone. The brand supports the execution of 32-bit and 64-bit Solaris 10 applications on either SPARC or x86 machines running the latest Solaris operating system.
The solaris10 brand supports the whole root non-global zone model. All of the required Solaris 10 software and any additional packages are installed into the private file systems of the zone.
The zone must reside on its own zfs(1M) dataset and only ZFS is supported. The ZFS dataset created automatically when the zone is installed or attached. If a ZFS dataset cannot be created, the zone is not installed or attached.
The zonecfg(1M) utility is used to configure a solaris10 branded zone. The SYSsolaris10 template can be used when creating the zone or the configuration can be set up manually. 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 support for delegated ZFS dataset configurations is currently experimental and has not yet been tested. Support for running these zones in a para-virtualized xVM domain is experimental and there are known problems with 64-bit x86 applications within the zone. The /dev/sound device cannot be configured into the branded zone. In addition, mdb(1) and dtrace(1M) are not fully functional when used in the global zone to examine processes executing within a solaris10 branded zone.
The solaris10 brand installer supports installing the zone from an image of an installed Solaris 10 system. This can be a full flash_archive(4), cpio(1), or pax(1) xustar archive. The cpio archive can be compressed with gzip(1) or bzip2(1). The image can also be a level 0 ufsdump(1M), or a path to the top-level of a Solaris 10 system's root directory tree. The zone cannot be installed from standard Solaris 10 distribution media.
To migrate a native zone from a Solaris 10 system to the latest Solaris Operating System kernel, the attach subcommand supports installing the zone from an archive of an installed Solaris 10 native zone. As with the installer, this can be a cpio(1) or pax(1) xustar archive of the zonepath. The cpio archive can be compressed with gzip(1) or bzip2(1). The image can also be a path to the top-level of a Solaris 10 zone's zonepath directory tree. In addition to migrating from a Solaris 10 native zone, the same migration options can be used when migrating a solaris10 branded zone from one host to another. When migrating from Solaris 10, it is possible that the zone is configured as a sparseroot zone. In this case, the zone should be readied on the host before the archive is made. This ensures that the inherited directories are included in the archive.
The following arguments of zoneadm(1M) brand-specific subcommand are supported:
Attach the specified Solaris 10 native zone image into the branded zone. If neither -a or -d is specified, the zone's zonepath is assumed to already be properly installed with the zone's files.
The path to a cpio(1), pax(1) xustar, or zfs archive of either an installed Solaris 10 native zone or a solaris10 branded zone's zonepath. cpio and zfs archives can be compressed using gzip or bzip2.
This option may not be used if the zone's state is 'unavailable'.
Warning: This option may be removed in a future release of Solaris. Use of 'zoneadm install -a archive' is suggested.
Specifying a sysidcfg file causes a sys-unconfig to occur on the zone after attach. The sysidcfg file is then applied to the zone.
The path to the zonepath directory of either an installed Solaris 10 native zone or a solaris10 branded zone's zonepath.
This option may not be used if the zone's state is 'unavailable'.
Warning: This option may be removed in a future release of Solaris. Use of 'zoneadm install -a archive' is suggested.
Install a zone by copying an existing installed zone. This subcommand is an alternative way to install the zone.
Provides a sysidcfg file to apply after unconfiguration of the cloned zone.
Install the specified Solaris 10 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 a flash_archive(4), cpio(1), pax(1) xustar, zfs archive, or a level 0 ufsdump(1M) of an installed Solaris 10 system, an installed Solaris 10 native zone, or a solaris10 branded zone. The cpio and zfs archives can be compressed using gzip or bzip2.
Provides a sysidcfg file to apply after installation.
The path to the root directory of an installed Solaris 10 system.
Preserve the system configuration after installing the zone.
Install silently.
Run sys-unconfig on the zone after installing it.
Verbose output from the install process.
The solaris10 zone only supports user-level Solaris 10 applications. You cannot use Solaris 10 device drivers or Solaris 10 kernel modules from inside a solaris10 zone. However, depending on the kernel module, you might be able to use the latest Solaris kernel module version with the Solaris 10 user-level application.
Example 1 Creating a ZFS Flash Archive for Install
The following example shows how to create an archive for a physical to virtual (P2V) migration. This is performed in the global zone of a system that is running Solaris 10. The Solaris 10 system must not have any non-global zones configured, installed, or running. The Solaris 10 system can use ZFS or UFS as its root file system.
# flarcreate -n s10box -c /net/somehost/p2v/s10box.flar
Example 2 Installing a solaris10 Branded Zone Using a Flash Archive
The following example installs a zone using the archive from Example 1. It assumes the zone has already been configured withzonecfg(1M) and has the brand property set to solaris10.
# zoneadm -z s10p2v install -a /net/somehost/p2v/s10box.flar -p
Example 3 Creating a ZFS Archive for Attach
The following example shows how to create an archive for a virtual to virtual (V2V) migration. It assumes that the zonepath for the solaris10 branded zone is /zones/v2vzone.
First, determine the name of zonepath dataset.
# dataset=$(zfs list -H -o name /zones/v2vzone)
Next, create a snapshot of the zone's datasets.
# zfs snapshot -r $dataset@v2v
Finally, generate a ZFS self-contained recursive stream that is compressed with bzip2.
# zfs send -rc $dataset@v2v | bzip2 > /net/somehost/v2v/v2v.zfs.bz2
Example 4 Attaching a Zone Using a ZFS Archive
The following example attaches a zone using a ZFS archive. It assumes that the zone has already been configured using zonecfg(1M) and that the brand property is set to solaris10.
# zoneadm -z v2vzone attach -a /net/somehost/v2v/v2v.zfs.bz2
See attributes(5) for a description of the following attributes:
|
cpio(1), mdb(1), pax(1), zlogin(1), dtrace(1M), ufsdump(1M), zfs(1M), zoneadm(1M), zonecfg(1M), flash_archive(4), attributes(5), brands(5), zones(5)
|