1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
|
=head1 NAME
xmdomain.cfg - xm domain config file format
=head1 SYNOPSIS
/etc/xen/myxendomain
/etc/xen/myxendomain2
/etc/xen/auto/myxenautostarted
=head1 DESCRIPTION
The B<xm>(1) program uses python executable config files to define
domains to create from scratch. Each of these config files needs to
contain a number of required options, and may specify many more.
Domain configuration files live in /etc/xen by default, if you store
config files anywhere else the full path to the config file must be
specified in the I<xm create> command.
/etc/xen/auto is a special case. Domain config files in that
directory will be started automatically at system boot if the
xendomain init script is enabled. The contents of /etc/xen/auto
should be symlinks to files in /etc/xen to allow I<xm create> to be
used without full paths.
Options are specified by I<name = value> statements in the
xmdomain.cfg files.
=head1 OPTIONS
The following lists the most commonly used options for a domain config
file.
=over 4
=item B<kernel>
The kernel image for the domain. The format of the parameter is the
fully qualified path to the kernel image file,
i.e. I</boot/vmlinuz-2.6.12-xenU>.
=item B<ramdisk>
The initial ramdisk for the domain. The format of the parameter is
the fully qualified path to the initrd, i.e. I</boot/initrd.gz>. On
many Linux distros you will not need a ramdisk if using the default
xen kernel.
=item B<memory>
The amount of RAM, in megabytes, to allocate to the domain when it
starts. Allocating insufficient memory for a domain may produce
extremely bizarre behavior. If there isn't enough free memory left on
the machine to fulfill this request, the domain will fail to start.
Xen does not support overcommit of memory, so the total memory of all
guests (+ 64 MB needed for Xen) must be less than or equal to the
physical RAM in the machine.
=item B<name>
A unique name for the domain. Attempting to create two domains with
the same name will cause an error.
=item B<root>
Specifies the root device for the domain. This is required for Linux
domains, and possibly other OSes.
=item B<nics>
The number of network interfaces allocated to the domain on boot. It
defaults to 1.
=item B<disk>
An array of block device stanzas, in the form:
disk = [ "stanza1", "stanza2", ... ]
Each stanza has 3 terms, seperated by commas,
"backend-dev,frontend-dev,mode".
=over 4
=item I<backend-dev>
The device in the backend domain that will be exported to the guest
(frontend) domain. Supported formats include:
I<phy:device> - export the physical device listed. The device can be
in symbolic form, as in sda7, or as the hex major/minor number, as in
0x301 (which is hda1).
I<file://path/to/file> - export the file listed as a loopback device.
This will take care of the loopback setup before exporting the device.
=item I<frontend-dev>
How the device should appear in the guest domain. The device can be
in symbolic form, as in sda7, or as the hex major/minor number, as in
0x301 (which is hda1).
=item I<mode>
The access mode for the device. There are currently 2 valid options,
I<r> (read-only), I<w> (read/write).
=back
=item B<vif>
An arrray of virtual interface stanzas in the form:
vif = [ "stanza1", "stanza2", ... ]
Each stanza specifies a set of I<name = value> options separated by
commas, in the form: "name1=value1, name2=value2, ..."
B<OPTIONS>
=over 4
=item I<bridge>
The network bridge to be used for this device. This is especially
needed if multiple bridges exist on the machine.
=item I<mac>
The MAC address for the virtual interface. If mac is not specified,
one will be randomly chosen by xen with the 00:16:3e vendor id prefix.
=back
=back
=head1 ADDITIONAL OPTIONS
The following options are also supported in the config file, though
are far more rarely used.
=over 4
=item B<builder>
Which builder should be used to construct the domain. This defaults
to the I<linux> if not specified, which is the builder for
paravirtualized Linux domains.
=item B<cpu>
Specifies which CPU the domain should be started on, where 0 specifies
the first cpu, 1 the second, and so on. This defaults to -1, which
means Xen is free to pick which CPU to start on.
=item B<extra>
Extra information to append to the end of the kernel parameter line.
The format is a string, the contents of which can be anything that the
kernel supports. For instance:
extra = "4"
Will cause the domain to boot to runlevel 4.
=item B<nfs_server>
The IP address of the NFS server to use as the root device for the
domain. In order to do this you'll need to specify I<root=/dev/nfs>,
and specify I<nfs_root>.
=item B<nfs_root>
The directory on the NFS server to be used as the root filesystem.
Specified as a fully qualified path, i.e. I</full/path/to/root/dir>.
=item B<vcpus>
The number of virtual cpus to allocate to the domain. In order to use
this the xen kernel must be compiled with SMP support.
This defaults to 1, meaning running the domain as a UP.
=back
=head1 DOMAIN SHUTDOWN OPTIONS
There are 3 options which control domain shutdown (both planned and
unplanned) under certain events. The 3 events currently captured are:
=over 4
=item B<on_shutdown>
Triggered on either an I<xm shutdown> or graceful shutdown from inside
the DomU.
=item B<on_reboot>
Triggered on either an I<xm reboot> or graceful reboot from inside the
DomU.
=item B<on_crash>
Triggered when a DomU goes to the crashed state for any reason.
=back
All of them take one of 4 valid states listed below.
=over 4
=item B<destroy>
The domain will be cleaned up completely. No attempt at respawning
will occur. This is what a typical shutdown would look like.
=item B<restart>
The domain will be restarted with the same name as the old domain.
This is what a typical reboot would look like.
=item B<preserve>
The domain will not be cleaned up at all. This is often useful for
crash state domains which ensures that enough evidence is to debug the
real issue.
=item B<rename-restart>
The old domain will not be cleaned up, but will be renamed so a new
domain can be restarted in it's place. The old domain will be renamed with
a suffix -1, -2, etc, and assigned a new random UUID; the new domain will
keep the original name and UUID. The old domain will release the devices that
it holds, so that the new one may take them.
=back
=head1 EXAMPLES
The following are quick examples of ways that domains might be
configured. They should not be considered an exhaustive set.
=over 4
=item I<A Loopback File as Root>
kernel = "/boot/vmlinuz-2.6-xenU"
memory = 128
name = "MyLinux"
root = "/dev/hda1 ro"
disk = [ "file:/var/xen/mylinux.img,hda1,w" ]
This creates a domain called MyLinux with 128 MB of memory using a
default xen kernel, and the file /var/xen/mylinux.img loopback mounted
at hda1, which is the root filesystem.
=item I<NFS Root>
FIXME: write me
=item I<LVM Root>
FIXME: write me
=item I<Two Networks>
FIXME: write me
=back
=head1 SEE ALSO
B<xm>(1)
=head1 AUTHOR
Sean Dague <sean at dague dot net>
=head1 BUGS
Not all options are currently documented
|
