File: switches.html

package info (click to toggle)
user-mode-linux-doc 20020523-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 1,592 kB
  • ctags: 340
  • sloc: makefile: 32
file content (622 lines) | stat: -rw-r--r-- 20,989 bytes parent folder | download
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
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
    "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
   <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<title>Kernel command line switches</title>
</head>
<body alink="#FF0000" vlink="#55188A" link="#0000EF" bgcolor="#FFFFFF" text="#000099">
<table border="0">
<tr align="left">
<td valign="top">
<table border="0">

<tr align="left"><td valign="top" >
<img width="120" height="171" src="uml-small.png">
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">
<font size="-1"><a href="index.html">Site Home Page</a></font>
<br>
              <font size="-1"><a href="uses.html">What it's good for</a></font>
<br>
              <font size="-1"><a href="case-studies.html">Case Studies</a></font>
<br>
              <font size="-1"><a href="kernel.html">Kernel Capabilities</a></font>
<br>
              <font size="-1"><a href="dl-sf.html">Downloading it</a></font>
<br>
              <font size="-1"><a href="run.html">Running it</a></font>
<br>
              <font size="-1"><a href="compile.html">Compiling</a></font>
<br>
              <font size="-1"><a href="install.html">Installation</a></font>
<br>
              <font size="-1"><a href="fs_making.html">Building filesystems</a></font>
<br>
              <font size="-1"><a href="faq.html">Troubles</a></font>
<br>
              <font size="-1"><a href="contrib.html">User Contributions</a></font>
<br>
              <font size="-1"><a href="links.html">Related Links</a></font>
<br>
              <font size="-1"><a href="todo.html">The ToDo list</a></font>
<br>
              <font size="-1"><a href="projects.html">Projects</a></font>
<br>
              <font size="-1"><a href="diary.html">Diary</a></font>
<br>
              <font size="-1"><a href="thanks.html">Thanks</a></font>
<br>
              <font size="-1"><a href="contacts.html">Contacts</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Tutorials<br>
<font size="-1"><a href="UserModeLinux-HOWTO.html">The HOWTO (html)</a></font>
<br>
              <font size="-1"><a href="UserModeLinux-HOWTO.txt">The HOWTO (text)</a></font>
<br>
              <font size="-1"><a href="hostfs.html">Host file access</a></font>
<br>
              <font size="-1"><a href="input.html">Device inputs</a></font>
<br>
              <font size="-1"><a href="shared_fs.html">Sharing filesystems</a></font>
<br>
              <font size="-1"><a href="fs.html">Creating filesystems</a></font>
<br>
              <font size="-1"><a href="networking.html">Virtual Networking</a></font>
<br>
              <font size="-1"><a href="mconsole.html">Management Console</a></font>
<br>
              <font size="-1"><a href="debugging.html">Kernel Debugging</a></font>
<br>
              <font size="-1"><a href="gprof.html">gprof and gcov</a></font>
<br>
              <font size="-1"><a href="xtut.html">Running X</a></font>
<br>
              <font size="-1"><a href="trouble.html">Diagnosing problems</a></font>
<br>
              <font size="-1"><a href="config.html">Configuration</a></font>
<br>
              <font size="-1"><a href="slack_readme.html">Installing Slackware</a></font>
<br>
              <font size="-1"><a href="arch-port.html">Porting UML</a></font>
<br>
              <font size="-1"><a href="iomem.html">IO memory emulation</a></font>
<br>
              <font size="-1"><a href="2G-2G.html">UML on 2G/2G hosts</a></font>
<br>
              <font size="-1"><a href="lksct/index.html">Adding a UML system call</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">How you can help<br>
<font size="-1"><a href="help-gen.html">Overview</a></font>
<br>
              <font size="-1"><a href="help-doc.html">Documentation</a></font>
<br>
              <font size="-1"><a href="help-userspace.html">Utilities</a></font>
<br>
              <font size="-1"><a href="help-kernel-v1.html">Kernel bugs</a></font>
<br>
              <font size="-1"><a href="projects.html">Kernel projects</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Screenshots<br>
<font size="-1"><a href="net.html">A virtual network</a></font>
<br>
              <font size="-1"><a href="x.html">An X session</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Transcripts<br>
<font size="-1"><a href="login.html">A login session</a></font>
<br>
              <font size="-1"><a href="debug-session.html">A debugging session</a></font>
<br>
              <font size="-1"><a href="slackinst.html">Slackware installation</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Reference<br>
<font size="-1"><a href="switches.html">Kernel switches</a></font>
<br>
              <font size="-1"><a href="slack_readme.html">Slackware README</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Papers<br>
<font size="-1"><a href="als2000/index.html">ALS 2000 paper (html)</a></font>
<br>
              <font size="-1"><a href="als2000.tex">ALS 2000 paper (TeX)</a></font>
<br>
              <font size="-1"><a href="slides/als2000/slides.html">ALS 2000 slides</a></font>
<br>
              <font size="-1"><a href="slides/lca2001/lca.html">LCA 2001 slides</a></font>
<br>
              <font size="-1"><a href="slides/ols2001/index.html">OLS 2001 paper (html)</a></font>
<br>
              <font size="-1"><a href="ols2001.tex">OLS 2001 paper (TeX)</a></font>
<br>
              <font size="-1"><a href="als2001/index.html">ALS 2001 paper (html)</a></font>
<br>
              <font size="-1"><a href="als2001.tex">ALS 2001 paper (TeX)</a></font>
<br>
              <font size="-1"><a href="slides/ists2002/umlsec.htm">UML security (html)</a></font>
<br>
              <font size="-1"><a href="slides/lca2002/lca2002.htm">LCA 2002 (html)</a></font>
<br>
              <font size="-1"><a href="slides/wvu2002/wvu2002.htm">WVU 2002 (html)</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Fun and Games<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/cgi-bin/hangman">Kernel Hangman</a></font>
<br>
              <font size="-1"><a href="sdotm.html">Disaster of the Month</a></font>
</td></tr>

</table>
</td>
<td valign="top" align="left">

<center>
            <h3>Kernel command line switches</h3>
          </center>
This is a list of the UML-specific command line arguments, plus a few
generic ones which deserve mention here.

<a name="--version"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">--version</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="--version">
This causes UML to print its version and exit.
</blockquote>

<a name="--help"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">--help</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="--help">
This causes UML to print a usage message and exit.
</blockquote>

<a name="con"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">con</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="con">
<b>con=<i>channel</i>
            </b> attaches one or more UML consoles to the
named channel.  The format of the channel is described
<a href="input.html">here</a>.
</blockquote>

<a name="debug"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">debug</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="debug">
Starts up the kernel under the control of gdb.  See the 
<a href="debugging.html">kernel debugging tutorial</a> and the 
<a href="debug-session.html">debugging session</a> pages for more
information.  Another form of this switch is <b>debug=go</b> which is the
same as <b>debug</b> except that the kernel runs instead of stopping at the
beginning of start_kernel.
</blockquote>

<a name="debugtrace"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">debugtrace</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="debugtrace">
Causes the tracing thread to pause until it is attached by a debugger
and continued.  This is mostly for debugging crashes early during
boot, and should be pretty much obsoleted by the <b>debug</b> switch.
</blockquote>

<a name="dsp"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">dsp</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="dsp">
<b>dsp=<i>host dsp</i>
            </b> tells the UML sound driver what the
filename of the host dsp is so that it can relay to it.  The default
is &quot;/dev/sound/dsp&quot;.
</blockquote>

<a name="eth"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">eth</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="eth">
<b>eth<i>n</i>=<i>host interface</i>
            </b> enables a virtual ethernet
device inside UML.  See the
<a href="networking.html">networking HOWTO</a>
for more information on setting up UML networking.
</blockquote>

<a name="fakehd"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">fakehd</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="fakehd">
Causes the ubd device to put its partition information in
/proc/partitions under the device name &quot;hd&quot; rather than &quot;ubd&quot;.  Again,
this is to fake out installation procedures which are overly picky in
their sanity-checking.
</blockquote>

<a name="fake_ide"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">fake_ide</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="fake_ide">
<b>fake_ide</b> causes the ubd driver to install realistic-looking
entries into /proc/ide.  This is useful for convincing some
distribution installation procedures to run inside UML.
</blockquote>

<a name="gdb"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">gdb</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="gdb">
<b>gdb=<i>channel</i>
            </b>, when used with <b>debug</b>, attaches gdb to the
named channel.  The format of the channel is described
<a href="input.html">here</a>.
</blockquote>

<a name="gdb-pid"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">gdb-pid</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="gdb-pid">
<b>gdb-pid=<i>pid</i>
            </b>, when used with <b>debug</b>, specifies the pid of
an already running debugger that UML should attach to.  This can be used
to debug UML with a gdb wrapper such as emacs or ddd, as well as with debuggers
other than gdb.  See the <a href="debugging.html">
debugging page</a> for more information.
</blockquote>

<a name="honeypot"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">honeypot</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="honeypot">
<b>honeypot</b> causes UML to rearrange its address space in order to
put process stacks in the same location as on the host.  This allows
stack smash exploits to work against UML just as they do against the
host.  This option enables <b>jail</b>, since it is most unlikely that
a honeypot UML should run without it enabled.
</blockquote>

<a name="initrd"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">initrd</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="initrd">
<b>initrd=<i>image</i>
            </b> sets the filename of the initrd image that
UML will boot from.
</blockquote>

<a name="iomem"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">iomem</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="iomem">
<b>iomem=<i>name</i>,<i>file</i>
            </b> makes <i>file</i> available to be
mapped by a driver inside UML.  See 
<a href="iomem.htl">this page</a> for more information.
</blockquote>

<a name="jail"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">jail</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="jail">
<b>jail</b> enables protection of UML kernel memory from UML
processes.  This is disabled by default for performance reasons.
Without it, it is fairly simple to break out of UML by changing the
right pieces of UML kernel data.
</blockquote>

<a name="mconsole"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">mconsole</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="mconsole">
<b>mconsole=notify:<i>socket</i>
            </b> asks the mconsole driver to send
the name of its socket to the Unix socket named by this switch.  This
is intended for the use of scripts which want to know when they can
start using the mconsole and what socket they should send commands to.
</blockquote>

<a name="mem"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">mem</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="mem">
<b>mem=<i>size</i>
            </b> controls how much &quot;physical&quot; memory the kernel 
allocates for the system.  The size is specified as a number followed by one 
of 'k', 'K&quot;, 'm', 'M&quot;, which have the obvious meanings.  This is not related
to the amount of memory in the physical machine.  It can be more, and
the excess, if it's ever used, will just be swapped out.
</blockquote>

<a name="mixer"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">mixer</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="mixer">
<b>mixer=<i>host mixer</i>
            </b> tells the UML sound driver what the
filename of the host mixer is so that it can relay to it.  The default
is &quot;/dev/sound/mixer&quot;.
</blockquote>

<a name="ncpus"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">ncpus</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="ncpus">
<b>ncpus=<i>number</i>
            </b> tells an SMP kernel how many virtual processors to 
start.  Currently, this has no effect because SMP isn't enabled.
</blockquote>

<a name="ssl"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">ssl</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="ssl">
<b>ssl=<i>channel</i>
            </b> attaches one or more UML serial lines to the
named channel.  The format of the channel is described
<a href="input.html">here</a>.
</blockquote>

<a name="root"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">root</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="root">
<b>root=<i>root device</i>
            </b> is actually used by the generic kernel in 
exactly the same way as in any other kernel.  If you configure a number of 
block devices and want to boot off something other than ubd0, you would use something like:
<blockquote>
              <tt>
                <font color="#000000">root=/dev/ubd5</font>
              </tt>
            </blockquote>
</blockquote>

<a name="ubd"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">ubd</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="ubd">
<b>ubd=<i>number</i>
            </b> causes the ubd device to take over a different major 
number than the one assigned to it.  This is useful for making it appear to 
be an &quot;hd&quot; device.
</blockquote>

<a name="ubd"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">ubd</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="ubd">
<b>ubd<i>n</i>=<i>filename</i>
            </b> is used to associate a device with a file 
in the underlying filesystem.  Usually, there is a filesystem in the file, 
but that's not required.  Swap devices containing swap files can be specified
like this.  Also, a file which doesn't contain a filesystem can have
its contents read in the virtual machine by running dd on the device.
n must be in the range 0 to 7.  Appending an 'r' to the number will
cause that device to be mounted read-only.
</blockquote>

<a name="ubd"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">ubd</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="ubd">
<b>ubd<i>n</i>=<i>cow-file,backing-file</i>
            </b> is used to layer a COW
file on another, possibly readonly, file.  This is useful in a number
of ways.  See <a href="shared_fs.html">this
page</a> for all the details.
</blockquote>

<a name="umid"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">umid</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="umid">
<b>umid=<i>name</i>
            </b> is used to assign a name to a virtual machine.  This
is intended to make it easy for UIs to manage multiple UMLs.  Currently, the
only effect of this is that UML writes its tracing thread pid in 
/tmp/uml/<i>name</i>.
</blockquote>

<a name="uml_dir"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">uml_dir</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="uml_dir">
<b>uml_dir=<i>directory</i>
            </b> sets the directory in which UML will
put the umid directory, which in turn will contain the pid file and
mconsole socket.
</blockquote>

<a name="umn"/><table width="100%" bgcolor="#e0e0e0">
            <tr>
              <td>
                <b>
                  <font color="black">umn</font>
                </b>
              </td>
            </tr>
          </table>
          <blockquote head="umn">
<b>umn=<i>ip-address</i>
            </b> sets the ip address of the host side of the slip 
device that the umn device configures.  This is necessary if you want to set up
networking, but your local net isn't 192.168.0.x, or you want to run
multiple virtual machines on a network, in which case, you need to
assign different ip addresses to the different machines.  See the 
<a href="networking.html">networking tutorial</a> for more information.
</blockquote>


</td>
</tr>
</table>

<center>
<font size="-1">
Hosted at </font>
<a href="http://sourceforge.net">
<IMG alt="SourceForge Logo" border="0" height="31" width="88" src="http://sourceforge.net/sflogo.php?group_id=429">
</a>
</center>
</body>
</html>