About Booting the solaris10 Branded Zone

Booting a zone places the zone in the running state. A zone can be booted from the ready state or from the installed state. A zone in the installed state that is booted transparently transitions through the ready state to the running state. Zone login is allowed for zones in the running state.

Note that you perform the internal zone configuration when you log in to the unconfigured zone for the first time after the initial boot.

Image sysidcfg Profile

If you created an Oracle Solaris 10 system archive from an existing system and use the -p (preserve sysidcfg) option when you install the zone, then the zone will have the same identity as the system used to create the image.

The -c option can be used to include a sysidcfg file to use in configuring the zone after the installation completes. To install a solaris10 zone, use a sysidcfg file in the command line. Note that a full path to the file must be supplied.

# zoneadm -z s10-zone install -a /net/machine_name/s10-system.flar -u -c /path_to/sysidcfg

The following sample sysidcfg file uses the net0 network name and timezone to configure an exclusive-IP zone with a static-IP configuration:

system_locale=C
 terminal=xterm
 network_interface=net0 {
    hostname=test7
    ip_address=192.168.0.101
    netmask=255.255.255.0
    default_route=NONE
    protocol_ipv6=no
 }
 name_service=NONE
 security_policy=NONE
 timezone=US/Pacific
 timeserver=localhost
 nfs4_domain=dynamic
 root_password=FSPXl81aZ7Vyo
 auto_reg=disable

The following sample sysidcfg file is used to configure a shared-IP zone:

system_locale=C
terminal=dtterm
network_interface=primary {
hostname=my-zone
}
security_policy=NONE
name_service=NIS {
domain_name=special.example.com
name_server=bird(192.168.112.3)
}
nfs4_domain=domain.com
timezone=US/Central
root_password=m4qtoWN

The following sample sysidcfg file is used to configure an exclusive-IP zone with a static IP configuration:

system_locale=C
terminal=dtterm
network_interface=primary {
hostname=my-zone
default_route=10.10.10.1
ip_address=10.10.10.13
netmask=255.255.255.0
}
nfs4_domain=domain.com
timezone=US/Central
root_password=m4qtoWN

The following sample sysidcfg file is used to configure an exclusive-IP zone with the DHCP and IPv6 option:

system_locale=C
terminal=dtterm
network_interface=primary {
dhcp protocol_ipv6=yes
}
security_policy=NONE
name_service=DNS {
domain_name=example.net
name_server=192.168.224.11,192.168.224.33
}
nfs4_domain=domain.com
timezone=US/Central
root_password=m4qtoWN

solaris10 Branded Zone Internal Configuration

When no profile is given, then the configuration tool will start on the first use of zlogin -C.

The name of the zone in this procedure is s10-zone.

1. Become root or assume an equivalent role.
2. In one terminal window, connect to the zone console, s10-zonein this procedure, before booting the zone by using the command:

   # zlogin -C s10-zone

3. In a second window, boot the zone as described in How to Boot the solaris10 Branded Zone.

How to Boot the solaris10 Branded Zone

You must be the global administrator or a user with the appropriate authorizations in the global zone to perform this procedure.

1. Become root or assume an equivalent role.
2. Use the zoneadm command with the -z option, the name of the zone, which is s10-zone, and the boot subcommand to boot the zone.

   global# zoneadm -z s10-zone boot

3. When the boot completes, use the list subcommand with the -v option to verify the status.

   global# zoneadm list -v

   You will see a display that is similar to the following:

   ID  NAME     STATUS       PATH                           BRAND      IP
    0  global   running     /                               solaris     shared
    1  s10-zone running     /zone/s10-zone                  solaris10   shared

See Also

For more information on booting zones and boot options, see Chapter 19, Installing, Booting, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks).