VirtualBox

Changeset 64214 in vbox


Ignore:
Timestamp:
Oct 11, 2016 6:41:38 PM (8 years ago)
Author:
vboxsync
svn:sync-xref-src-repo-rev:
111212
Message:

bugref:8530: Documentation: improve automated instructions for building kernel modules: try to make instructions in the documentation more fool-proof, giving precise names of header packages instead of describing how to construct the name.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/user_Installation.xml

    r64095 r64214  
    354354
    355355    <sect2 id="externalkernelmodules">
    356       <title>The VirtualBox kernel module</title>
    357 
    358       <para>VirtualBox uses a special kernel module called
    359       <computeroutput>vboxdrv</computeroutput> to perform physical memory
    360       allocation and to gain control of the processor for guest system
    361       execution. Without this kernel module, you can still use the VirtualBox
    362       manager to configure virtual machines, but they will not start. In
    363       addition, there are the network kernel modules
     356      <title>The VirtualBox driver modules</title>
     357
     358      <para>In order to run other operating systems in virtual machines
     359      alongside your main operating system, VirtualBox needs to integrate
     360      very tightly into the system.  To do this it installs a "driver"
     361      module called <computeroutput>vboxdrv</computeroutput> which does
     362      a lot of the work. Without this kernel module, you can still use the
     363      VirtualBox manager to configure virtual machines, but they will not
     364      start. It also installs network drivers called
    364365      <computeroutput>vboxnetflt</computeroutput> and
    365       <computeroutput>vboxnetadp</computeroutput> which are required for the
    366       more advanced networking features of VirtualBox.</para>
     366      <computeroutput>vboxnetadp</computeroutput> which let virtual machines
     367      make more use of your computer's network capabilities.</para>
    367368
    368369      <para>The modules will be built automatically during installation or
     
    372373      <para>Most Linux distributions can be set up simply by installing
    373374      the right packages - normally, these will be the GNU compiler
    374       (GCC), GNU Make (make) and packages containing header files for
     375      (GCC), GNU Make (make) and packages containing "header files" for
    375376      your kernel - and making sure that all system updates are
    376377      installed and that the system is running the most up-to-date
    377       kernel included in the distribution. <emphasis>The version numbers
    378       of the header file packages must be the same as that of the kernel
    379       you are using.</emphasis></para>
     378      kernel included in the distribution. <emphasis>The running kernel
     379      and the header files must be updated to matching versions.</emphasis>
     380      We will give some instructions for common distributions.  For most
     381      of them you will want to start by finding the version name of your
     382      kernel using the command
     383      <computeroutput>uname -r</computeroutput> in a terminal.  They
     384      assume that you have not changed too much from the original
     385      installation, particularly not installed a different kernel type.
     386      If you have then you will need to determine yourself what to set
     387      up.</para>
    380388
    381389      <itemizedlist>
    382390        <listitem>
    383           <para>With Debian and Ubuntu releases, you must install the
    384           right version of the
    385           <computeroutput>linux-headers</computeroutput> and if it
    386           exists the <computeroutput>linux-kbuild</computeroutput>
    387           package. Current Ubuntu releases should have the right
     391          <para>With Debian and Ubuntu-based distributions, you
     392          must install the right version of the
     393          <computeroutput>linux-headers</computeroutput>, usually
     394          whichever of <computeroutput>linux-headers-generic
     395          </computeroutput>, <computeroutput>linux-headers-amd64
     396          </computeroutput>, <computeroutput>linux-headers-i686
     397          </computeroutput> or <computeroutput>linux-headers-i686-pae
     398          </computeroutput> best matches the kernel version name;
     399          and if it exists the <computeroutput>linux-kbuild
     400          </computeroutput>
     401          package. Basic Ubuntu releases should have the right
    388402          packages installed by default.</para>
    389403        </listitem>
    390404
    391405        <listitem>
    392           <para>In even older Debian and Ubuntu releases, you must
    393           install the right version of the
    394           <computeroutput>kernel-headers</computeroutput>
    395           package.</para>
    396         </listitem>
    397 
    398         <listitem>
    399           <para>On Fedora and Redhat systems, the package is
     406          <para>On Fedora, Redhat, Oracle Linux and many other
     407          RPM-based systems, the kernel version sometimes has
     408          a code of letters or a word close to the end of the
     409          version name, for example "uek" for the Oracle
     410          Enterprise kernel or "default" or "desktop" for the
     411          standard SUSE kernels.  In this case the package name is
     412          <computeroutput>kernel-uek-devel</computeroutput> or
     413          equivalent.  If there is no such code, it is usually
    400414          <computeroutput>kernel-devel</computeroutput>.</para>
    401415        </listitem>
    402416
    403417        <listitem>
    404           <para>On SUSE and openSUSE Linux, you must install the right
    405           versions of the <computeroutput>kernel-source</computeroutput>
     418          <para>On older SUSE and openSUSE Linux, you must install
     419          the <computeroutput>kernel-source</computeroutput>
    406420          and <computeroutput>kernel-syms</computeroutput>
    407421          packages.</para>
    408         </listitem>
    409 
    410         <listitem>
    411           <para>If you have built your own kernel, you will need to make
    412           sure that you also installed all the required header and other
    413           files for building external modules to the right locations.
    414           The details of how to do this will depend on how you built
    415           your kernel, and if you are unsure you should consult the
    416           documentation which you followed to do so.</para>
    417422        </listitem>
    418423      </itemizedlist>
Note: See TracChangeset for help on using the changeset viewer.

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