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
|
<!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>The Kernel</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>The Kernel</h3>
</center>
UML is a fully-functional Linux kernel. It runs its own scheduler and
VM system, relying on the host kernel only for the equivalent of hardware
support.
<p>
The virtual machine is completely configurable through the command
line, allowing its memory, available devices, and their configurations
to be specified. The available command line switches are described
<a href="switches.html">here</a>.
<p>
<a name="Hardware support"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">Hardware support</font>
</b>
</td>
</tr>
</table>
<blockquote head="Hardware support">
UML hardware support comes in the form of virtual devices which use
resources on the host. It supports all the usual types of devices
that a physical system does:
<ul>
<li>
Block devices - UML block devices are normally associated with a file
on the host which contains a filesystem. This file is made to look
like a block device inside the virtual machine, and the filesystem on
it is mounted just as a filesystem on a physical disk is mounted in a
native kernel. A block device file may also contain a swap signature,
in which case, UML will be willing to swap onto it. It can also be
treated as a raw disk, which isn't mounted, but instead has data read
from and written to it with a utility such as dd.
<p>
Block devices can also be attached to anything on the host which resembles
a file. Examples include CD-ROMS, floppies, physical disks and
partitions, and memory devices such as /dev/mem.
<p>
UML block devices can be layered, with a read-only device having a
copy-on-write (COW) read-write device on top of it. This acts as a
single read-write device, with the modifications to the read-only
layer being recorded in the read-write COW layer. This allows
multiple machines to share a filesystem, allowing a large saving in
disk space on the host. If you are doing development, and plan on
crashing UML frequently, then COW-ing your root filesystem allows you
to avoid fscking it on each boot by deleting the COW file and reusing
the clean backing file. This is described further
<a href="shared_fs.html">here</a>.
</li>
<li>
Consoles and serial lines - These are almost identical, sharing most
of their code, and differing only where they need to present different
interfaces to the rest of the kernel. They can be attached to a
number of different interfaces on the host, including file
descriptors, ptys, ttys, pts devices, and xterms. More information
about this is <a href="input.html">here</a>.
<p>
By default, the main console is attached to file descriptors 0 and 1
(stdin and stdout), the other consoles come up in xterms, and the
serial lines attach themselves to ptys.
</li>
<li>
Network devices - Similarly, the network driver can use a variety of
host interfaces to exchange packets with other virtual machines, the
host, and the rest of the network. To construct a completely virtual
network, with no access to the host networking, UML can use a hub
daemon to forward packets from one virtual machine to another or it
can set up a multicast network and have the machines send packets
directly to each other. To access the host and the outside network,
UML can use either ethertap or slip interfaces on the host. A more
complete description of this is
<a href="networking.html">here</a>.
</li>
</ul>
</blockquote>
<a name="Hot-plugging devices"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">Hot-plugging devices</font>
</b>
</td>
</tr>
</table>
<blockquote head="Hot-plugging devices">
The <a href="mconsole.html">management console</a> is a
low-level interface into the kernel. Among other things, it allows
UML devices to be added to and removed from a running system.
Currently, the block devices and network devices can be hot-plugged.
In time, this will be extended to the rest of the devices, so you will
be able to construct, destroy, and rebuild essentially the entire
system without having to reboot it.
</blockquote>
<a name="Generic kernel functionality"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">Generic kernel functionality</font>
</b>
</td>
</tr>
</table>
<blockquote head="Generic kernel functionality">
UML runs its scheduler independently of the host scheduler - the host
scheduler simply implements the decisions made by the UML scheduler.
Similarly, UML runs its own VM system, allocating backing memory from
a pool that it considers to be physical memory, mapping that memory as
needed into its process virtual address spaces and its own virtual
memory. If needed, and it has swap configured, it will swap.
<p>
Basically, anything in Linux that's not hardware-specific just works.
This includes kernel modules, the filesystems, software devices, and
network protocols.
</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>
|
