2 .\" Copyright (c) 2003, 2004, 2005, 2006, 2007
3 .\" The DragonFly Project. All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in
13 .\" the documentation and/or other materials provided with the
15 .\" 3. Neither the name of The DragonFly Project nor the names of its
16 .\" contributors may be used to endorse or promote products derived
17 .\" from this software without specific, prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
20 .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
21 .\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
22 .\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
23 .\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
24 .\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING,
25 .\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
26 .\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
27 .\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
28 .\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
29 .\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" $DragonFly: src/share/man/man7/vkernel.7,v 1.15 2007/04/20 07:04:09 swildner Exp $
41 .Nd virtual kernel architecture
43 .Cd "platform vkernel"
47 .Pa /usr/obj/usr/src/sys/VKERNEL/kernel.debug
49 .Op Fl e Ar name Ns = Ns Li value : Ns Ar name Ns = Ns Li value : Ns ...
51 .Op Fl I Ar interface Ns Op Ar :address1 Ns Oo Ar :address2 Oc Ns Oo Ar /netmask Oc
57 architecture allows for running
61 The following options are available:
62 .Bl -tag -width ".Fl m Ar size"
63 .It Fl e Ar name Ns = Ns Li value : Ns Ar name Ns = Ns Li value : Ns ...
64 Specify an environment to be used by the kernel.
66 Specify a memory image
68 to be used by the virtual kernel.
71 option is given, the kernel will generate a name of the form
72 .Pa /var/vkernel/memimg.XXXXXX ,
75 being replaced by a sequential number, e.g.\&
77 .It Fl I Ar interface Ns Op Ar :address1 Ns Oo Ar :address2 Oc Ns Oo Ar /netmask Oc
78 Create a virtual network device, with the first
88 argument is the name of a
93 path prefix does not have to be specified and will be automatically prepended.
96 will pick the first unused
104 arguments are the IP addresses of the
115 interface is added to the specified
121 argument applies to all interfaces for which an address is specified.
123 Specify the amount of memory to be used by the kernel in bytes,
131 Lowercase versions of
139 to be used by the kernel, with the first
147 Boot into single-user mode.
149 Enable writing to kernel memory and module loading.
150 By default, those are disabled for security reasons.
152 Turn on verbose booting.
155 A number of virtual device drivers exist to supplement the virtual kernel.
156 Their names start with
161 driver allows for up to 16
164 The root device will be
168 for further information on how to prepare a root image).
169 .Ss Network interface
172 driver supports up to 16 virtual network interfaces which are associated with
177 device, the per-interface read only
180 .Va hw.vke Ns Em X Ns Va .tap_unit
181 holds the unit number of the associated
185 The virtual kernel enables all terminal signals while in
187 mode but only enables
190 while operating as a console which causes the virtual kernel to enter its
195 It is possible to directly gdb the virtual kernel's process.
196 It is recommended that you do a
197 .Ql handle SIGSEGV noprint
198 to ignore page faults processed by the virtual kernel itself.
200 A couple of steps are necessary in order to prepare the system to build and
201 run a virtual kernel.
202 .Ss Setting up the filesystem
205 architecture needs a number of files which reside in
207 Since these files tend to get rather big and the
209 partition is usually of limited size, we recommend the directory to be
212 partition with a link to it in
215 mkdir /home/var.vkernel
216 ln -s /home/var.vkernel /var/vkernel
219 Next, a filesystem image to be used by the virtual kernel has to be
220 created and populated (assuming world has been built previously):
222 dd if=/dev/zero of=/var/vkernel/rootimg.01 bs=1m count=2048
223 vnconfig -c -s labels vn0 /var/vkernel/rootimg.01
224 disklabel -r -w vn0 auto
225 disklabel -e vn0 # edit the label to create a vn0a partition
229 make installworld DESTDIR=/mnt
231 make distribution DESTDIR=/mnt
232 echo '/dev/vkd0a / ufs rw 1 1' >/mnt/etc/fstab
233 echo 'console "/usr/libexec/getty Pc" cons25 on secure' >/mnt/etc/ttys
237 .Ss Compiling the virtual kernel
238 In order to compile a virtual kernel use the
240 kernel configuration file residing in
241 .Pa /usr/src/sys/config
242 (or a configuration file derived thereof):
245 make -DNO_MODULES buildkernel KERNCONF=VKERNEL
247 .Ss Enabling virtual kernel operation
250 .Va vm.vkernel_enable ,
251 must be set to enable
255 sysctl vm.vkernel_enable=1
257 .Ss Configuring the network on the host system
258 In order to access a network interface of the host system from the
260 you must add the interface to a
262 device which will then be passed to the
268 ifconfig bridge0 create
269 ifconfig bridge0 addm re0 # assuming re0 is the host's interface
272 .Ss Running the kernel
273 Finally, the virtual kernel can be run:
275 cd /usr/obj/usr/src/sys/VKERNEL
276 \&./kernel.debug -m 64m -r /var/vkernel/rootimg.01 -I auto:bridge0
281 command can be used to stop a virtual kernel.
291 Virtual kernels were introduced in
296 thought up and implemented the
298 architecture and wrote the
305 This manual page was written by