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.26 2007/07/11 00:49:05 swildner Exp $
41 .Nd virtual kernel architecture
43 .Cd "platform vkernel"
47 .Pa /usr/obj/usr/src/sys/VKERNEL/kernel.debug
50 .Op Fl e Ar name Ns = Ns Li value : Ns Ar name Ns = Ns Li value : Ns ...
52 .Op Fl I Ar interface Ns Op Ar :address1 Ns Oo Ar :address2 Oc Ns Oo Ar /netmask Oc
61 architecture allows for running
65 The following options are available:
66 .Bl -tag -width ".Fl m Ar size"
68 Specify a readonly CD-ROM image
70 to be used by the kernel, with the first
80 option specified on the command line will be the boot disk.
81 The CD9660 filesystem is assumed when booting from this media.
82 .It Fl e Ar name Ns = Ns Li value : Ns Ar name Ns = Ns Li value : Ns ...
83 Specify an environment to be used by the kernel.
85 Specify a memory image
87 to be used by the virtual kernel.
90 option is given, the kernel will generate a name of the form
91 .Pa /var/vkernel/memimg.XXXXXX ,
94 being replaced by a sequential number, e.g.\&
96 .It Fl I Ar interface Ns Op Ar :address1 Ns Oo Ar :address2 Oc Ns Oo Ar /netmask Oc
97 Create a virtual network device, with the first
107 argument is the name of a
112 path prefix does not have to be specified and will be automatically prepended.
115 will pick the first unused
123 arguments are the IP addresses of the
134 interface is added to the specified
140 argument applies to all interfaces for which an address is specified.
142 Specify which, if any, real CPUs to lock virtual CPUs to.
146 .Cm map Ns Op Ns , Ns Ar startCPU ,
151 does not map virtual CPUs to real CPUs.
154 .Cm map Ns Op Ns , Ns Ar startCPU
155 maps each virtual CPU to a real CPU starting with real CPU 0 or
160 locks all virtual CPUs to the real CPU specified by
163 Specify the amount of memory to be used by the kernel in bytes,
171 Lowercase versions of
177 Specify the number of CPUs you wish to emulate.
178 Up to 32 CPUs are supported.
179 The virtual kernel must be built with
181 to use this option and will default to 2 CPUs unless otherwise specified.
183 Specify a file in which to store the process ID.
184 A warning is issued if this file cannot be opened for writing.
186 Specify a R/W disk image
188 to be used by the kernel, with the first
198 option specified on the command line will be the boot disk.
200 Boot into single-user mode.
202 Enable writing to kernel memory and module loading.
203 By default, those are disabled for security reasons.
205 Turn on verbose booting.
208 A number of virtual device drivers exist to supplement the virtual kernel.
209 Their names start with
214 driver allows for up to 16
217 The root device will be
221 for further information on how to prepare a root image).
222 .Ss Network interface
225 driver supports up to 16 virtual network interfaces which are associated with
230 device, the per-interface read only
233 .Va hw.vke Ns Em X Ns Va .tap_unit
234 holds the unit number of the associated
238 The virtual kernel only enables
242 while operating in regular console mode.
246 to the virtual kernel causes the virtual kernel to enter its internal
248 debugger and re-enable all other terminal signals.
251 to the virtual kernel triggers a clean shutdown by passing a
253 to the virtual kernel's
257 It is possible to directly gdb the virtual kernel's process.
258 It is recommended that you do a
259 .Ql handle SIGSEGV noprint
260 to ignore page faults processed by the virtual kernel itself.
262 A couple of steps are necessary in order to prepare the system to build and
263 run a virtual kernel.
264 .Ss Setting up the filesystem
267 architecture needs a number of files which reside in
269 Since these files tend to get rather big and the
271 partition is usually of limited size, we recommend the directory to be
274 partition with a link to it in
277 mkdir /home/var.vkernel
278 ln -s /home/var.vkernel /var/vkernel
281 Next, a filesystem image to be used by the virtual kernel has to be
282 created and populated (assuming world has been built previously):
284 dd if=/dev/zero of=/var/vkernel/rootimg.01 bs=1m count=2048
285 vnconfig -c -s labels vn0 /var/vkernel/rootimg.01
286 disklabel -r -w vn0s0 auto
287 disklabel -e vn0s0 # edit the label to create a vn0s0a partition
289 mount /dev/vn0s0a /mnt
291 make installworld DESTDIR=/mnt
293 make distribution DESTDIR=/mnt
294 echo '/dev/vkd0a / ufs rw 1 1' >/mnt/etc/fstab
301 entry with the following line and turn off all other gettys.
303 console "/usr/libexec/getty Pc" cons25 on secure
306 Then, unmount the disk.
311 .Ss Compiling the virtual kernel
312 In order to compile a virtual kernel use the
314 kernel configuration file residing in
315 .Pa /usr/src/sys/config
316 (or a configuration file derived thereof):
319 make -DNO_MODULES buildkernel KERNCONF=VKERNEL
321 .Ss Enabling virtual kernel operation
324 .Va vm.vkernel_enable ,
325 must be set to enable
329 sysctl vm.vkernel_enable=1
331 .Ss Configuring the network on the host system
332 In order to access a network interface of the host system from the
334 you must add the interface to a
336 device which will then be passed to the
342 ifconfig bridge0 create
343 ifconfig bridge0 addm re0 # assuming re0 is the host's interface
346 .Ss Running the kernel
347 Finally, the virtual kernel can be run:
349 cd /usr/obj/usr/src/sys/VKERNEL
350 \&./kernel.debug -m 64m -r /var/vkernel/rootimg.01 -I auto:bridge0
355 command can be used to stop a virtual kernel.
356 .Sh BUILDING THE WORLD UNDER A VKERNEL
357 The virtual kernel platform does not have all the header files expected
358 by a world build, so the easiest thing to do right now is to specify a
359 pc32 target when building the world under a virtual kernel, like this:
361 vkernel# make MACHINE_PLATFORM=pc32 buildworld
362 vkernel# make MACHINE_PLATFORM=pc32 installworld
373 Virtual kernels were introduced in
378 thought up and implemented the
380 architecture and wrote the
387 This manual page was written by