VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/externalkernelmodules.dita@ 105482

Last change on this file since 105482 was 105289, checked in by vboxsync, 7 months ago

Docs: bugref:10705. Merging current changes to dita files from docs team's repo. (r6123, r6120, r6117)

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 4.0 KB
Line 
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
3<topic xml:lang="en-us" id="externalkernelmodules">
4 <title>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Kernel Modules</title>
5
6 <body>
7 <p>In order to run other operating systems in virtual machines alongside your main operating system, <ph
8 conkeyref="vbox-conkeyref-phrases/product-name"/> needs to integrate very tightly with your system. To do this
9 it installs a driver module called <userinput>vboxdrv</userinput> into the system kernel. The kernel is the part
10 of the operating system which controls your processor and physical hardware. Without this kernel module, you can
11 still use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to configure virtual machines, but they will not
12 start. </p>
13 <p>Network drivers called <userinput>vboxnetflt</userinput> and <userinput>vboxnetadp</userinput> are also
14 installed. They enable virtual machines to make more use of your computer's network capabilities and are needed
15 for any virtual machine networking beyond the basic NAT mode. </p>
16 <p>Since distributing driver modules separately from the kernel is not something which Linux supports well, the <ph
17 conkeyref="vbox-conkeyref-phrases/product-name"/> install process creates the modules on the system where they
18 will be used. This means that you may need to install some software packages from the distribution which are
19 needed for the build process. Required packages may include the following: </p>
20 <ul>
21 <li>
22 <p>GNU compiler (GCC) </p>
23 </li>
24 <li>
25 <p>GNU Make (make) </p>
26 </li>
27 <li>
28 <p>Kernel header files </p>
29 </li>
30 </ul>
31 <p>Also ensure that all system updates have been installed and that your system is running the most up-to-date
32 kernel for the distribution. </p>
33 <note>
34 <p>The running kernel and the kernel header files must be updated to matching versions. </p>
35 </note>
36 <p>The following list includes some details of the required files for some common distributions. Start by finding
37 the version name of your kernel, using the command <userinput>uname -r</userinput> in a terminal. The list assumes
38 that you have not changed too much from the original installation, in particular that you have not installed a
39 different kernel type. </p>
40 <ul>
41 <li>
42 <p>With Debian and Ubuntu-based distributions, you must install the correct version of the
43 <filepath>linux-headers</filepath>, usually whichever of <filepath>linux-headers-generic</filepath>,
44 <filepath>linux-headers-amd64</filepath>, <filepath>linux-headers-i686</filepath> or
45 <filepath>linux-headers-i686-pae</filepath> best matches the kernel version name. Also, the
46 <filepath>linux-kbuild</filepath> package if it exists. Basic Ubuntu releases should have the correct
47 packages installed by default. </p>
48 </li>
49 <li>
50 <p>On Fedora, Red Hat, Oracle Linux and many other RPM-based systems, the kernel version sometimes has a code of
51 letters or a word close to the end of the version name. For example "uek" for the Oracle Unbreakable
52 Enterprise Kernel or "default" or "desktop" for the standard kernels. In this case, the package name is
53 <filepath>kernel-uek-devel</filepath> or equivalent. If there is no such code, it is usually
54 <filepath>kernel-devel</filepath>. </p>
55 </li>
56 <li>
57 <p>On some SUSE and openSUSE Linux versions, you may need to install the <filepath>kernel-source</filepath> and
58 <filepath>kernel-syms</filepath> packages. </p>
59 </li>
60 </ul>
61 <p>If you suspect that something has gone wrong with module installation, check that your system is set up as
62 described above and try running the following command, as root: </p>
63 <pre xml:space="preserve">rcvboxdrv setup</pre>
64 </body>
65</topic>
Note: See TracBrowser for help on using the repository browser.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette