Changeset 62238 in vbox for trunk/doc/manual
- Timestamp:
- Jul 14, 2016 10:09:08 AM (9 years ago)
- svn:sync-xref-src-repo-rev:
- 108751
- Location:
- trunk/doc/manual/en_US
- Files:
-
- 3 edited
-
user_Glossary.xml (modified) (1 diff)
-
user_GuestAdditions.xml (modified) (2 diffs)
-
user_Installation.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Glossary.xml
r54330 r62238 117 117 machine when networking is configured to NAT; see <xref 118 118 linkend="networkingdetails" />.</para> 119 </glossdef>120 </glossentry>121 122 <glossentry>123 <glossterm>DKMS</glossterm>124 125 <glossdef>126 <para>Dynamic Kernel Module Support. A framework that simplifies127 installing and updating external kernel modules on Linux machines; see128 <xref linkend="externalkernelmodules" />.</para>129 119 </glossdef> 130 120 </glossentry> -
trunk/doc/manual/en_US/user_GuestAdditions.xml
r60719 r62238 595 595 on a Linux host system, as described there.</para> 596 596 597 <para>Again, as with Linux hosts, we recommend using DKMS if it is 598 available for the guest system. If it is not installed, use this 599 command for Ubuntu/Debian systems: 600 <screen>sudo apt-get install dkms</screen> 601 or for Fedora systems: <screen>yum install dkms</screen></para> 602 603 <para>Be sure to install DKMS <emphasis>before</emphasis> 604 installing the Linux Guest Additions. If DKMS is not available 605 or not installed, the guest kernel modules will need to be 606 recreated manually whenever the guest kernel is updated using 607 the command <screen>rcvboxadd setup</screen> as root. 608 </para> 597 <para>If you suspect that something has gone wrong, check that your 598 guest is set up correctly and try executing the command 599 <screen>rcvboxadd setup</screen> as root.</para> 609 600 </listitem> 610 601 … … 625 616 </listitem> 626 617 </orderedlist> 627 628 <para>For your convenience, we provide the following step-by-step629 instructions for freshly installed copies of recent versions of the most630 popular Linux distributions. After these preparational steps, you can631 execute the VirtualBox Guest Additions installer as described632 above.</para>633 634 <sect4>635 <title>Ubuntu</title>636 637 <para><orderedlist>638 <listitem>639 <para>In order to fully update your guest system, open a640 terminal and run <screen>apt-get update</screen> as root641 followed by <screen>apt-get upgrade</screen></para>642 </listitem>643 644 <listitem>645 <para>Install DKMS using <screen>apt-get install dkms</screen></para>646 </listitem>647 648 <listitem>649 <para>Reboot your guest system in order to activate the650 updates and then proceed as described above.</para>651 </listitem>652 </orderedlist></para>653 </sect4>654 655 <sect4>656 <title>Fedora</title>657 658 <para><orderedlist>659 <listitem>660 <para>In order to fully update your guest system, open a661 terminal and run <screen>yum update</screen> as root.</para>662 </listitem>663 664 <listitem>665 <para>Install DKMS and the GNU C compiler using <screen>yum install dkms</screen>666 followed by <screen>yum install gcc</screen></para>667 </listitem>668 669 <listitem>670 <para>Reboot your guest system in order to activate the671 updates and then proceed as described above.</para>672 </listitem>673 </orderedlist></para>674 </sect4>675 676 <sect4>677 <title>openSUSE</title>678 679 <para><orderedlist>680 <listitem>681 <para>In order to fully update your guest system, open a682 terminal and run <screen>zypper update</screen> as root.</para>683 </listitem>684 685 <listitem>686 <para>Install the make tool and the GNU C compiler using687 <screen>zypper install make gcc</screen></para>688 </listitem>689 690 <listitem>691 <para>Reboot your guest system in order to activate the692 updates.</para>693 </listitem>694 695 <listitem>696 <para>Find out which kernel you are running using <screen>uname -a</screen>697 An example would be698 <computeroutput>2.6.31.12-0.2-default</computeroutput> which699 refers to the "default" kernel. Then install the correct700 kernel development package. In the above example this would be701 <screen>zypper install kernel-default-devel</screen></para>702 </listitem>703 704 <listitem>705 <para>Make sure that your running kernel706 (<computeroutput>uname -a</computeroutput>) and the kernel707 packages you have installed (<computeroutput>rpm -qa708 kernel\*</computeroutput>) have the exact same version number.709 Proceed with the installation as described above.</para>710 </listitem>711 </orderedlist></para>712 </sect4>713 714 <sect4>715 <title>SuSE Linux Enterprise Desktop (SLED)</title>716 717 <para><orderedlist>718 <listitem>719 <para>In order to fully update your guest system, open a720 terminal and run <screen>zypper update</screen> as root.</para>721 </listitem>722 723 <listitem>724 <para>Install the GNU C compiler using <screen>zypper install gcc</screen></para>725 </listitem>726 727 <listitem>728 <para>Reboot your guest system in order to activate the729 updates.</para>730 </listitem>731 732 <listitem>733 <para>Find out which kernel you are running using <screen>uname -a</screen>734 An example would be735 <computeroutput>2.6.27.19-5.1-default</computeroutput> which736 refers to the "default" kernel. Then install the correct737 kernel development package. In the above example this would be738 <screen>zypper install kernel-syms kernel-source</screen></para>739 </listitem>740 741 <listitem>742 <para>Make sure that your running kernel743 (<computeroutput>uname -a</computeroutput>) and the kernel744 packages you have installed (<computeroutput>rpm -qa745 kernel\*</computeroutput>) have the exact same version number.746 Proceed with the installation as described above.</para>747 </listitem>748 </orderedlist></para>749 </sect4>750 751 <sect4>752 <title>Mandrake</title>753 754 <para><orderedlist>755 <listitem>756 <para>Mandrake ships with the VirtualBox Guest Additions which757 will be replaced if you follow these steps.</para>758 </listitem>759 760 <listitem>761 <para>In order to fully update your guest system, open a762 terminal and run <screen>urpmi --auto-update</screen>763 as root.</para>764 </listitem>765 766 <listitem>767 <para>Reboot your system in order to activate the768 updates.</para>769 </listitem>770 771 <listitem>772 <para>Install DKMS using <screen>urpmi dkms</screen> and make773 sure to choose the correct kernel-devel package when asked by774 the installer (use <computeroutput>uname -a</computeroutput>775 to compare).</para>776 </listitem>777 </orderedlist></para>778 </sect4>779 780 <sect4>781 <title>Oracle Linux, Red Hat Enterprise Linux and CentOS</title>782 783 <para><orderedlist>784 <listitem>785 <para>For versions prior to 6, add <computeroutput>divider=10</computeroutput>786 to the kernel boot options in787 <computeroutput>/etc/grub.conf</computeroutput> to reduce the788 idle CPU load.</para>789 </listitem>790 791 <listitem>792 <para>In order to fully update your guest system, open a793 terminal and run <screen>yum update</screen> as root.</para>794 </listitem>795 796 <listitem>797 <para>Install the GNU C compiler and the kernel development798 packages using <screen>yum install gcc</screen> followed by799 <screen>yum install kernel-devel</screen> For Oracle UEK800 kernels, use <screen>yum install kernel-uek-devel</screen>801 to install the UEK kernel headers.</para>802 </listitem>803 804 <listitem>805 <para>Reboot your guest system in order to activate the806 updates and then proceed as described above.</para>807 </listitem>808 809 <listitem>810 <para>In case Oracle Linux does not find the811 required packages, you either have to install them from a812 different source (e.g. DVD) or use Oracle's public Yum server813 located at <ulink814 url="http://public-yum.oracle.com/">http://public-yum.oracle.com</ulink>.</para>815 </listitem>816 </orderedlist></para>817 </sect4>818 819 <sect4>820 <title>Debian</title>821 822 <para><orderedlist>823 <listitem>824 <para>In order to fully update your guest system, open a825 terminal and run <screen>apt-get update</screen> as root826 followed by <screen>apt-get upgrade</screen></para>827 </listitem>828 829 <listitem>830 <para>Install the make tool and the GNU C compiler using831 <screen>apt-get install make gcc</screen></para>832 </listitem>833 834 <listitem>835 <para>Reboot your guest system in order to activate the836 updates.</para>837 </listitem>838 839 <listitem>840 <para>Determine the exact version of your kernel using841 <computeroutput>uname -a</computeroutput> and install the842 correct version of the linux-headers package, e.g. using843 <screen>apt-get install linux-headers-2.6.26-2-686</screen></para>844 </listitem>845 </orderedlist></para>846 </sect4>847 618 </sect3> 848 619 -
trunk/doc/manual/en_US/user_Installation.xml
r61889 r62238 366 366 more advanced networking features of VirtualBox.</para> 367 367 368 <para>The VirtualBox kernel module is automatically installed on your 369 system when you install VirtualBox. To maintain it with future kernel 370 updates, for those Linux distributions which provide it -- most current 371 ones -- we recommend installing Dynamic Kernel Module Support 372 (DKMS)<footnote> 373 <para>See <ulink 374 url="http://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support">http://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support</ulink> 375 for an introduction.</para> 376 </footnote>. This framework helps with building and upgrading kernel 377 modules.</para> 378 379 <para>If DKMS is not already installed, execute one of the following: 368 <para>The modules will be built automatically during installation or 369 after kernel updates if your Linux system is prepared for building 370 external kernel modules.</para> 371 372 <para>Most Linux distributions can be set up simply by installing 373 the right packages - normally, these will be the GNU compiler 374 (GCC), GNU Make (make) and packages containing header files for 375 your kernel - and making sure that all system updates are 376 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> 380 380 381 <itemizedlist> 381 <listitem> 382 <para>On an Ubuntu system:</para> 383 384 <screen>sudo apt-get install dkms</screen> 385 </listitem> 386 387 <listitem> 388 <para>On a Fedora system:<screen>yum install dkms</screen></para> 389 </listitem> 390 391 <listitem> 392 <para>On a Mandriva or Mageia system:<screen>urpmi dkms</screen></para> 393 </listitem> 394 </itemizedlist></para> 395 396 <para>If DKMS is available and installed, the VirtualBox kernel module 397 should always work automatically, and it will be automatically rebuilt 398 if your host kernel is updated.</para> 399 400 <para>Otherwise, there are only two situations in which you will need to 401 worry about the kernel module:<orderedlist> 402 <listitem> 403 <para>The original installation fails. This probably means that 404 your Linux system is not prepared for building external kernel 405 modules.</para> 406 407 <para>Most Linux distributions can be set up simply by installing 408 the right packages - normally, these will be the GNU compiler 409 (GCC), GNU Make (make) and packages containing header files for 410 your kernel - and making sure that all system updates are 411 installed and that the system is running the most up-to-date 412 kernel included in the distribution. <emphasis>The version numbers 413 of the header file packages must be the same as that of the kernel 414 you are using.</emphasis></para> 415 416 <itemizedlist> 417 <listitem> 418 <para>With Debian and Ubuntu releases, you must install the 419 right version of the 420 <computeroutput>linux-headers</computeroutput> and if it 421 exists the <computeroutput>linux-kbuild</computeroutput> 422 package. Current Ubuntu releases should have the right 423 packages installed by default.</para> 424 </listitem> 425 426 <listitem> 427 <para>In even older Debian and Ubuntu releases, you must 428 install the right version of the 429 <computeroutput>kernel-headers</computeroutput> 430 package.</para> 431 </listitem> 432 433 <listitem> 434 <para>On Fedora and Redhat systems, the package is 435 <computeroutput>kernel-devel</computeroutput>.</para> 436 </listitem> 437 438 <listitem> 439 <para>On SUSE and openSUSE Linux, you must install the right 440 versions of the <computeroutput>kernel-source</computeroutput> 441 and <computeroutput>kernel-syms</computeroutput> 442 packages.</para> 443 </listitem> 444 445 <listitem> 446 <para>If you have built your own kernel, you will need to make 447 sure that you also installed all the required header and other 448 files for building external modules to the right locations. 449 The details of how to do this will depend on how you built 450 your kernel, and if you are unsure you should consult the 451 documentation which you followed to do so.</para> 452 </listitem> 453 </itemizedlist> 454 </listitem> 455 456 <listitem> 457 <para>The kernel of your Linux host was updated and DKMS is not 458 installed. In that case, the kernel module will need to be 459 reinstalled by executing (as root):</para> 460 461 <screen>rcvboxdrv setup</screen> 462 </listitem> 463 </orderedlist></para> 382 <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 388 packages installed by default.</para> 389 </listitem> 390 391 <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 400 <computeroutput>kernel-devel</computeroutput>.</para> 401 </listitem> 402 403 <listitem> 404 <para>On SUSE and openSUSE Linux, you must install the right 405 versions of the <computeroutput>kernel-source</computeroutput> 406 and <computeroutput>kernel-syms</computeroutput> 407 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> 417 </listitem> 418 </itemizedlist> 419 420 <para>If you suspect that something has gone wrong with module installation, 421 check that your system is set up as described above and try running (as root) 422 the following command:</para> 423 424 <screen>rcvboxdrv setup</screen> 464 425 </sect2> 465 426
Note:
See TracChangeset
for help on using the changeset viewer.
