Sun Microsystems manual ID Name Status Path Brand, 100

Version 3.1-enSolaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009

Now, zone test1 is configured in exactly the same way as zone test but has its own zonepath.

global# zonecfg -z test1 info zonename: test1

zonepath: /container/test1

brand: native

autoboot: false bootargs: pool: limitpriv: scheduling-class: ip-type: shared inherit-pkg-dir:

dir: /lib inherit-pkg-dir:

dir: /platform

inherit-pkg-dir: dir: /sbin

inherit-pkg-dir: dir: /usr inherit-pkg-dir: dir: /opt

global# zoneadm list -vc
ID	NAME	STATUS	PATH	BRAND	IP
0	global	running	/	native	shared
-	test	installed	/container/test	native	shared
-	test1	configured	/container/test1	native	shared

Next, zone test1, which so far has only been configured, can be installed by duplicating the zone test. Zone test1 can be used immediately afterwards.

global# zoneadm -z test1		clone test
Cloning zonepath	/container/test...
grep: can't open	/a/etc/dumpadm.conf
global#
global# zoneadm -z test1		boot
root@se-ffm-03-um-test [283] # zoneadm list -vc
ID NAME	STATUS	PATH	BRAND	IP
0 global	running	/	native	shared
25 test1	running	/container/test1	native	shared
- test	installed /container/test		native	shared

In this example, no network is configured for zone test, which is of course unrealistic in thereal world. If a network is configured, it must be of course reconfigured after configuring the zone test1 like the zonepath was reconfigured, since otherwise both zones will have the same network address and be unable to run simultaneously.

100