Changeset 105289 in vbox for trunk/doc/manual/en_US/dita/topics/externalkernelmodules.dita
- Timestamp:
- Jul 12, 2024 9:07:43 AM (6 months ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/externalkernelmodules.dita
r99797 r105289 5 5 6 6 <body> 7 <p> 8 In order to run other operating systems in virtual machines 9 alongside your main operating system, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to 10 integrate very tightly with your system. To do this it installs 11 a driver module called <userinput>vboxdrv</userinput> into the 12 system kernel. The kernel is the part of the operating system 13 which controls your processor and physical hardware. Without 14 this kernel module, you can still use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to configure 15 virtual machines, but they will not start. 16 </p> 17 <p> 18 Network drivers called <userinput>vboxnetflt</userinput> and 19 <userinput>vboxnetadp</userinput> are also installed. They enable 20 virtual machines to make more use of your computer's network 21 capabilities and are needed for any virtual machine networking 22 beyond the basic NAT mode. 23 </p> 24 <p> 25 Since distributing driver modules separately from the kernel is 26 not something which Linux supports well, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 27 install process creates the modules on the system where they 28 will be used. This means that you may need to install some 29 software packages from the distribution which are needed for the 30 build process. Required packages may include the following: 31 </p> 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> 32 20 <ul> 33 21 <li> 34 <p> 35 GNU compiler (GCC) 36 </p> 22 <p>GNU compiler (GCC) </p> 37 23 </li> 38 24 <li> 39 <p> 40 GNU Make (make) 41 </p> 25 <p>GNU Make (make) </p> 42 26 </li> 43 27 <li> 44 <p> 45 Kernel header files 46 </p> 28 <p>Kernel header files </p> 47 29 </li> 48 30 </ul> 49 <p> 50 Also ensure that all system updates have been installed and that 51 your system is running the most up-to-date kernel for the 52 distribution. 53 </p> 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> 54 33 <note> 55 <p> 56 The running kernel and the kernel header files must be updated 57 to matching versions. 58 </p> 34 <p>The running kernel and the kernel header files must be updated to matching versions. </p> 59 35 </note> 60 <p> 61 The following list includes some details of the required files 62 for some common distributions. Start by finding the version name 63 of your kernel, using the command <userinput>uname -r</userinput> in 64 a terminal. The list assumes that you have not changed too much 65 from the original installation, in particular that you have not 66 installed a different kernel type. 67 </p> 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> 68 40 <ul> 69 41 <li> 70 <p> 71 With Debian and Ubuntu-based distributions, you must install 72 the correct version of the 73 <filepath>linux-headers</filepath>, usually whichever of 74 <filepath>linux-headers-generic</filepath>, 75 <filepath>linux-headers-amd64</filepath>, 76 <filepath>linux-headers-i686</filepath> or 77 <filepath>linux-headers-i686-pae</filepath> best matches the 78 kernel version name. Also, the 79 <filepath>linux-kbuild</filepath> package if it exists. 80 Basic Ubuntu releases should have the correct packages 81 installed by default. 82 </p> 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> 83 48 </li> 84 49 <li> 85 <p> 86 On Fedora, Red Hat, Oracle Linux and many other RPM-based 87 systems, the kernel version sometimes has a code of letters 88 or a word close to the end of the version name. For example 89 "uek" for the Oracle Unbreakable Enterprise Kernel or 90 "default" or "desktop" for the standard kernels. In this 91 case, the package name is 92 <filepath>kernel-uek-devel</filepath> or equivalent. If 93 there is no such code, it is usually 94 <filepath>kernel-devel</filepath>. 95 </p> 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> 96 55 </li> 97 56 <li> 98 <p> 99 On some SUSE and openSUSE Linux versions, you may need to 100 install the <filepath>kernel-source</filepath> and 101 <filepath>kernel-syms</filepath> packages. 102 </p> 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> 103 59 </li> 104 60 </ul> 105 <p> 106 If you suspect that something has gone wrong with module 107 installation, check that your system is set up as described 108 above and try running the following command, as root: 109 </p> 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> 110 63 <pre xml:space="preserve">rcvboxdrv setup</pre> 111 64 </body>
Note:
See TracChangeset
for help on using the changeset viewer.
