The following files are used to configure and install non-global zones:
Required. The config file is the zone's configuration in file form from the output of the zonecfg export command.
The location of the config file is specified by the source attribute of the configuration element in the AI manifest. AI copies this config file onto the installed client system to be used to configure the zone.
Optional. This AI manifest for zone installation specifies packages to be installed in the zone, along with publisher information and certificate and key files as necessary. See Non-Global Zone AI Manifest for information about creating a custom AI manifest for a zone.
To provide a custom AI manifest for a zone, add the manifest to the install service that is installing the global zone. In the create-manifest command, specify the zonename criteria keyword with the names of all zones that should use this AI manifest.
If you do not provide a custom AI manifest for a non-global zone, the default AI manifest for zones is used, as shown in Example 12–1.
Optional. You can provide zero or more system configuration profiles for a non-global zone. These profiles are similar to the profiles for configuring the global zone. See Chapter 11, Configuring the Client System for information about system configuration profile files. You might want to provide profiles to specify zone configuration such as users and the root password for the zone administrator. See Non-Global Zone System Configuration Profiles for an example profile for a non-global zone.
To provide system configuration profiles for a zone, add the profiles to the install service that is installing the global zone. In the create-profile command, specify the zonename criteria keyword with the names of all zones that should use this profile.
If you do not provide any system configuration profile files, the system configuration interactive tool runs and queries for required data on first boot of the zone. See Reconfiguring a System for information about using the interactive configuration tool.
The following example adds the /tmp/zmanifest.xml AI manifest to the solaris11_2-sparc install service and specifies that zone1 and zone2 should use this manifest.
# installadm create-manifest -n solaris11_2-sparc -f /tmp/zmanifest.xml \ -m zmanifest -c zonename="zone1 zone2"
The following example adds the /tmp/z1profile.xml profile to the solaris11_2-sparc install service and specifies that zone1 and zone2 should use this profile.
# installadm create-profile -n solaris11_2-sparc -f /tmp/z1profile.xml \ -p z1profile -c zonename="zone1 zone2"
The following example adds the /tmp/z2profile.xml profile to the solaris11_2-sparc install service and specifies that zone2 should use this profile.
# installadm create-profile -n solaris11_2-sparc -f /tmp/z2profile.xml \ -p z2profile -c zonename=zone2
The following example shows the AI manifests and system configuration profiles that have been added to the solaris11_2-sparc install service.
$ installadm list -n solaris11_2-sparc -m -p
Service Name Manifest Name Type Status Criteria
------------ ------------- ---- ------ --------
solaris11_2-sparc line1-netra2000 xml active mac = 00:14:4F:2D:7A:DC
zmanifest xml active zonename = zone1,zone2
orig_default derived default none
Service Name Profile Name Criteria
------------ ------------ --------
solaris11_2-sparc z1profile zonename = zone1,zone2
z2profile zonename = zone2