Wiki code for BrandZ Installation

Hide Line numbers
1: = 1. Overview
2: 
3: This document describes:
4: 
5: * How to obtain and install the Solaris™ Express: Community Release required to run a Linux application in a branded non-global zone on your system
6: * How to configure, install, boot, and log in to the non-global zone that will support the execution of Linux (lx branded) binaries
7: 
8: = 2. System Requirements
9: 
10: Your machine must be running the Solaris Express: Community Release. The following primary machine considerations are associated with the use of lx branded zones.
11: 
12: * The machine must be either x64 or x86 based.
13: * Sufficient disk space to hold the files that are unique within each lx zone must be available. The disk space requirements for an lx zone are determined by the size and number of RPMs (Linux packages) that are installed. The lx brand supports only the whole root model, so each installed zone will have its own copy of every file.
14: 
15: There are no limits on how much disk space can be consumed by a zone. The global administrator is responsible for space restriction. The global administrator must ensure that local storage is sufficient to hold a non-global zone’s root file system. Even a small uniprocessor system can support a number of zones running simultaneously.
16: 
17: If you intend to install a Linux zone from a standard distribution, whether from CD media or the associated ISO images, please be aware that the lx brand installer currently only supports Red Hat Enterprise Linux 3.x and the equivalent CentOS distributions.
18: 
19: If you intend to install a Linux zone from a filesystem tarball other than the one available on the OpenSolaris site, please be aware that the lx brand emulates the 2.4.21 kernel and glibc 2.3, as modified by Red Hat. Distros based on other versions of either may or may not work.3. Installing the BrandZ Solaris Build Now that BrandZ has integrated into Solaris, this whole section has been obsoleted.
20: 
21: =  4. Before You Begin the Zone Configuration
22: 
23: This section describes the information you must collect before you can configure a zone, and covers the format of the zonecfg command.
24: 
25: == 4.1 Determine the Zone Name and Path
26: 
27: You must choose a name and a path for your zone.
28: 
29: The zone name identifies the zone to the configuration utility. The following rules apply to zone names:
30: 
31: * Each zone must have a unique name.
32: * A zone name is case-sensitive.
33: * A zone name must begin with an alpha-numeric character.
34: * The name can contain alpha-numeric characters, underbars (_), hyphens (-), and periods (.).
35: * The name cannot be longer than 64 characters.
36: * The name global and all names beginning with SUNW are reserved and cannot be used.
37: 
38:  The zonepath property is the path to the zone root. The system creates the directory with the correct permissions.
39: 
40: == 4.2 Obtain the Network Address
41: 
42: Each zone that requires network connectivity has one or more unique IP addresses. You must assign an IPv4 address or manually configure and assign an IPv6 address for the zone.
43: 
44: The IP address must be specified in the //slash// format. For example, for an address of 10.6.10.233 with a netmask of 255.255.255.0, you would specify the address as 10.6.10.233/24.
45: 
46: == 4.3 About Using the zonecfg Command
47: 
48: The zonecfg command is used to create the zone configuration.
49: 
50: The zonecfg prompt is of the following form:
51: 
52: {{{
53: 
54: zonecfg:zonename>
55: 
56: }}}
57: 
58: When you are configuring a specific resource type, such as a network interface resource, that resource type is also included in the prompt:
59: 
60: {{{
61: 
62: zonecfg:zonename:net>
63: 
64: }}}
65: 
66: =  5. How to Configure the lx Branded Zone
67: 
68: You must be the global administrator in the global zone to perform this procedure. Note that steps 5-8 are optional. These steps only need to be performed if you want to add a network interface to the zone.
69: 
70: === Steps
71: 
72: 1. Become superuser, or assume the Primary Administrator role.
73: 1. Set up a zone configuration with the zone name you have chosen.
74: The name myzone is used in this example procedure.
75: 
76: {{{
77:  global# **zonecfg -z myzone**
78: }}}
79: 
80:  If this is the first time you have configured this zone, you will see the following system message:
81: 
82: {{{
83:  myzone: No such zone configured
84: Use ’create’ to begin configuring a new zone.
85: }}}
86: 
87: 1. Create the new zone configuration for the lx zone.
88: 
89: {{{
90:  zonecfg:my-zone> **create -t SUNWlx**
91: }}}
92: 
93: 1. Set the zone path, /export/my-zone_root in this procedure.
94: 
95: {{{
96:  zonecfg:myzone> **set zonepath=/export/myzone_root**
97: }}}
98: 
99: 1. (Optional) Configure a network device in the zone.
100: 1* Add a network virtual interface.
101: 
102: {{{
103: zonecfg:myzone> **add net**
104: }}}
105: 
106: 1* Set the address in the form < //ip address of zone>/<netmask>//. In this procedure, 10.6.10.233/24 is used.
107: 
108: {{{
109:         zonecfg:myzone:net> **set address=****10.6.10.233/24**
110: }}}
111: 
112: 1* Set the physical device type for the network interface, the bge device in this procedure.
113: 
114: {{{
115:  zonecfg:myzone:net> **set physical=bge0**
116: }}}
117: 
118: 1* End the net specification.
119: 
120: {{{
121:  zonecfg:myzone:net> **end**
122: }}}
123: 
124: 1. (Optional) Enable the audio device in the zone. (NOTE: this requires that a working audio device be present in the global zone.)
125: 
126: {{{
127:         zonecfg:myzone> **add attr**
128:         zonecfg:myzone:attr> **set name="audio"**
129:         zonecfg:myzone:attr> **set type=boolean**
130:         zonecfg:myzone:attr> **set value=true**
131:         zonecfg:myzone:attr> **end**
132: }}}
133: 
134: 1. Commit the zone configuration for the zone.
135: 
136: {{{
137:  zonecfg:myzone> **commit**
138: }}}
139: 
140: 1. Exit the zonecfg command.
141: 
142: {{{
143:  zonecfg:myzone:net> **exit**
144: }}}
145: 
146:  Note that even if you did not explicitly type commit at the prompt, a commit is automatically attempted when you type exit or an EOF occurs.
147: 
148: **Tip:** The zonecfg command also supports multiple subcommands, quoted and separated by semicolons, from the same shell invocation. Type as one line.
149: 
150: {{{
151: 
152: global# **zonecfg -z myzone "create -t SUNWlx; set zonepath=/export/myzone_root"**
153: 
154: }}}
155: 
156: = 6. How to Install the lx Zone
157: 
158: You must be the global administrator in the global zone to perform this procedure.
159: 
160: **Steps**
161: 
162: 1. Become superuser, or assume the Primary Administrator role.
163: 1. If you intend to install from CD, you must enable volfs on your system and verify that it is running.
164: 
165: {{{
166: global# **svcadm enable svc:/system/filesystem/volfs:default**
167: }}}
168: 
169: {{{
170: global# **svcs | grep volfs**
171: }}}
172: 
173:  You will see a display similar to the following:
174: 
175: {{{
176: online      17:30 svc:/system/filesystem/volfs:default
177: }}}
178: 
179: 1. Install the zone using one of the following methods. Note that if the -d option is not specified, a CD installation is performed by default.
180: 1* Install the zone from a tarball:
181: 
182: {{{
183: global# **zoneadm -z myzone install -d **//<path to tarball>//
184: }}}
185: 
186: A tarball based on the [[CentOS Linux distribution>>http://centos.org]] is available on the OpenSolaris website in [[http://opensolaris.org/os/community/brandz/downloads>>Community Group brandz.downloads]].
187: 1* Install the zone from Red Hat or CentOS CDs, for example, /cdrom/cdrom0:
188: 
189: {{{
190: global# **zoneadm -z myzone install -d** **/cdrom/cdrom0**
191: }}}
192: 
193: 1* Install the zone from ISO images of Red Hat or CentOS install media:
194: 
195: {{{
196: global# **zoneadm -z myzone install -d** //<path to directory containing ISO images>//
197: }}}
198: 
199: You will see system messages as the non-global zone is installed.
200: **Note:** When installing from CD or ISO images, you can install a subset of the packages available on the install media. The available subsets are: **core**, **server**, **desktop**, **developer**, and **all**. Each cluster in this list includes the packages in all previous clusters. So, the ’desktop’ cluster includes everything in ’core’ and ’server’, as well as the packages useful for a developer.
201: For example, to install the server packages, type:
202: 
203: {{{
204: global# **zoneadm -z myzone install -d** //<install path>// **server**
205: }}}
206: 
207: 1. Verify the status of the zone.
208: 
209: {{{
210: global# **zoneadm list -iv**
211: }}}
212: 
213:  You will see a display similar to the following:
214: 
215: {{{
216:         ID NAME       STATUS        PATH                  BRAND
217:         0  global     running       /                     native
218:         1  myzone     installed     /export/zones/myzone  lx
219: }}}
220: 
221: = 7. How to Boot the lx Zone
222: 
223: You must be the global administrator in the global zone to perform this procedure.
224: 
225: **Steps**
226: 
227: 1. Become superuser, or assume the Primary Administrator role.
228: 1. Boot the zone.
229: 
230: {{{
231: global# **zoneadm -z myzone boot**
232: }}}
233: 
234: 1. Verify the status of the zone.
235: 
236: {{{
237: global# **zoneadm list -iv**
238: }}}
239: 
240: You will see a display similar to the following:
241: 
242: {{{
243:         ID NAME      STATUS      PATH                  BRAND
244:         0  global    running     /                     native
245:         1  myzone    running     /export/zones/myzone  lx
246: }}}
247: 
248: = 8. How to Log In to the lx Zone
249: 
250: You must be the global administrator in the global zone to perform this procedure.
251: 
252: **Steps**
253: 
254: 1. Become superuser, or assume the Primary Administrator role.
255: 1. Log in to the zone myzone.
256: 
257: {{{
258: global# **zlogin myzone**
259: }}}
260: 
261: You will see a display similar to the following:
262: 
263: {{{
264:  [Connected to zone ’myzone’ pts/2]
265: You have mail.
266: #
267: }}}
268: 
269: 1. Verify that you are running in a Linux environment under Solaris.
270: 
271: {{{
272:  [root@myzone root]# **uname -a**
273: }}}
274: 
275: You will see a display similar to the following:
276: 
277: {{{
278:  Linux myzone 2.4.21 BrandZ fake linux i686 i686 i386 GNU/Linux
279: }}}
280: 
281: 1. To exit the zone, type:
282: 
283: {{{
284: # **exit**
285: }}}
286: 
287:  You will see a display similar to the following:
288: 
289: {{{
290:  [Connection to zone ’myzone’ pts/2 closed]
291: }}}
292: 
293: = 9. How to Enable Networking in an lx Zone
294: 
295: When you install an lx branded zone, networking is disabled. To enable networking, edit the /etc/sysconfig/network file in the zone as follows:
296: 
297: {{{
298: NETWORKING=yes
299: HOSTNAME=//<hostname>//
300: }}}
301: 
302: To set up a NIS domain, add a line similar to the following:
303: 
304: {{{
305: NISDOMAIN=//<Grp.South.Sun.COM>//
306: }}}
307: 
308: If you are not using NIS, modify the /etc/nsswitch.conf file to use files or the DNS naming services for hostname lookups.
OpenSolaris

Top Menu

Wiki code for BrandZ Installation

Search

Collectives

Community Group

Project

User Group

Subsites

Community Group brandz Pages
