VirtualBox 4.2.12 on Fedora 18/17, CentOS/Red Hat (RHEL) 6.4/5.9

Oracle VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. VirtualBox is a general-purpose full virtualizer for x86 hardware. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software.

VirtualBox supports a large number of guest operating systems:

  • Windows 3.x
  • Windows NT 4.0
  • Windows 2000
  • Windows XP
  • Windows Server 2003
  • Windows Vista
  • Windows 7
  • DOS
  • Linux (2.4, 2.6, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7)
  • Solaris
  • OpenSolaris
  • OpenBSD

This guide shows howto install VirtualBox 4.2 (currently 4.2.12) on Fedora 18/17/16/15, CentOS 6.4/6.3/5.9, Red Hat (RHEL) 6.4/6.3/6.2/6.1/6/5.9. This guide uses Virtual Box own yum repositories.

Note: Fedora 14 users can install VirtualBox 4.1, Fedora 13 users can install VirtualBox 4.0 and Fedora 12 users can install VirtualBox 3.2.

1. Change to root User

su -
## OR ##
sudo -i

2. Install Fedora or RHEL Repo Files

cd /etc/yum.repos.d/
 
## Fedora 18/17/16/15/14/13/12 users
wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo
 
## CentOS 6.4/6.3/6.2/6.1/6/5.9 and Red Hat (RHEL) 6.4/6.3/6.2/6.1/6/5.9 users
wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo

3. Update latest packages and check your kernel version

Update packages

yum update

Check that that you are running latest installed kernel version
Output of following commands version numbers should match:

rpm -qa kernel |sort |tail -n 1
 
uname -r

Note: If you got kernel update or run older kernel than newest installed then reboot:

reboot

4. Install following dependency packages

CentOS 6/5 and Red Hat (RHEL) 6/5 needs EPEL repository, install it with following command:

## CentOS 6 and RHEL 6 ##
rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
 
## CentOS 5 and RHEL 5 ##
rpm -Uvh http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms
 
## PAE kernel users install ##
yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-PAE-devel dkms

5. Install VirtualBox Latest Version 4.2 (currently 4.2.12)

yum install VirtualBox-4.2

Note:
This command create automatically vboxusers group and VirtualBox user must be member of that group.
This command also build needed kernel modules.

Rebuild kernel modules with following command:

/etc/init.d/vboxdrv setup
## OR ##
service vboxdrv setup

6. Add VirtualBox User(s) to vboxusers Group

Replace user_name with your own user name or some another real user name.

usermod -a -G vboxusers user_name

7. Start VirtualBox

Use launcher from menu or simply run:

VirtualBox

Troubleshooting

If you have problems with KERN_DIR parameter or your kernel directory is not automatically detected then set KERN_DIR environment variable manually, using following method:

## Current running kernel on Fedora ##
KERN_DIR=/usr/src/kernels/`uname -r`
 
## Current running kernel on CentOS and Red Hat (RHEL) ##
KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`
 
## Fedora example ##
KERN_DIR=/usr/src/kernels/2.6.33.5-124.fc13.i686
 
## CentOS and Red Hat (RHEL) example ##
KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64
 
## Export KERN_DIR ##
export KERN_DIR

Check also:

Install VirtualBox Guest Additions on Fedora, CentOS, Red Hat (RHEL)

Follow If Not True Then False Updates!

332 Comments

  1. Hey JR

    Thanks for your support, I updated the kernel to 3.3 and compiled the drivers with /etc/init.d/vboxdrv setup and all went fine! thanks a lot!

    • Hello Tracker,

      You are welcome! Excellent to hear that you got it working! :D

  2. i can’t use “wget” command on my fedora 16. why…?

    • Hi abu,

      Install it with:

      yum install wget

      Then try again… :)

  3. Trying to register the VirtualBox kernel modules using DKMSError! Bad return status for module build on kernel: 3.3.0-8.fc16.x86_64 (x86_64)

    =(

    Anyone has some good ideas?

    • Hi Dandoloo,

      Please post output of following commands:

      rpm -qa kernel* |sort
       
      uname -a
      • i got this for my kernel not working response. i am a different person than who u were originally talking to.

        kernel-3.3.4-5.fc17.x86_64
        kernel-3.5.4-2.fc17.x86_64
        kernel-headers-3.5.4-2.fc17.x86_64
        [root@linuxmob yum.repos.d]# uname -a
        Linux linuxmob 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7 17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
        [root@linuxmob yum.repos.d]#

        • Hi linuxman,

          Just reboot and select 3.5.4 kernel in Grub menu.

          Then try again. Please let me know if you any other problems?

          • Thank you, i did not realize that when i reboot i needed to select that kernal version! it worked, i really appreciate the time you took to write this tutorial, and the fact that you helped with my issue. Thank you very much my friend!

            • Excellent! You are very welcome sergis!

  4. Thanks so much, vmware was working my nerves. Maybe you can do a tut for installing vmware on fedora 16 also. If you have one, link me there please. Thanks again

  5. Please help me out with this, hope all info is enough for Solution.

    [root@linuz kernels]# VirtualBox
    WARNING: The vboxdrv kernel module is not loaded. Either there is no module
    available for the current kernel (3.1.0-7.fc16.x86_64) or it failed to
    load. Please recompile the kernel module and install it by

    sudo /etc/init.d/vboxdrv setup

    You will not be able to start VMs until this problem is fixed.

    #service vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMSError! echo
    Your kernel headers for kernel 3.1.0-7.fc16.x86_64 cannot be found at
    /lib/modules/3.1.0-7.fc16.x86_64/build or /lib/modules/3.1.0-7.fc16.x86_64/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]

    ###/var/log/vbox-install.log
    Uninstalling modules from DKMS
    removing old DKMS module vboxhost version 4.1.12

    ——————————
    Deleting module version: 4.1.12
    completely from the DKMS tree.
    ——————————
    Done.
    Attempting to install using DKMS

    Creating symlink /var/lib/dkms/vboxhost/4.1.12/source ->
    /usr/src/vboxhost-4.1.12

    DKMS: add completed.
    Failed to install using DKMS, attempting to install without
    Makefile:172: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again. Stop.

    i tried with this but this doesn’t help me out, i think Kernel version is the issue, Kindly help me out with it..

    [root@linuz kernels]# KERN_DIR=/usr/src/kernels/3.3.1-3.fc16.x86_64/

    [root@linuz kernels]# ls -al /usr/src/kernels
    total 12
    drwxr-xr-x. 3 root root 4096 Apr 12 06:45 .
    drwxr-xr-x. 4 root root 4096 Apr 12 06:36 ..
    drwxr-xr-x 22 root root 4096 Apr 12 06:45 3.3.1-3.fc16.x86_64

    [root@linuz kernels]# rpm -qa | grep kernel | sort
    abrt-addon-kerneloops-2.0.7-2.fc16.x86_64
    kernel-3.1.0-7.fc16.x86_64
    kernel-3.3.1-3.fc16.x86_64
    kernel-devel-3.3.1-3.fc16.x86_64
    libreport-plugin-kerneloops-2.0.8-4.fc16.x86_64

    • Hi Jawad,

      Almost everything needed info and everything looks good, but you didn’t tell which kernel you are currently running?

      uname -a

      I guess that the just reboot is enough to get it working… ;)

  6. Ok, perfect! It works! :o) tks

  7. Thanks a lot.
    Greetings.

  8. Excellent guide – use it alot.

  9. Gracias, fue de gran ayuda…!!

  10. THanks a lot for the info.
    Greetings

  11. Thanks, I love it. But a get two warnings. Is this a problem?

    [root@maria-pc yum.repos.d]# VirtualBox
    Qt WARNING: QGtkStyle was unable to detect the current GTK+ theme.
    Qt WARNING: Qt: Session management error: None of the authentication protocols specified are supported
    [root@maria-pc yum.repos.d]#

    • Hi silvana,

      What system you are using?

  12. Hi, when updated to the new version 4.1.16 i get this error

    Failed to install the Extension Pack Oracle_VM_VirtualBox_Extension_Pack-4.1.6-78094.vbox-extpack. The installer failed with exit code 127: The value for the SHELL variable was not found the /etc/shells file This incident has been reported.. Result Code: NS_ERROR_FAILURE (0×80004005) Component: ExtPackManager Interface: IExtPackManager

    and then i have install it from command line like this:

    # VBoxManage extpack install –replace Oracle_VM_VirtualBox_Extension_Pack-4.1.6-74713.vbox-extpack
    0%…10%…20%…30%…40%…50%…60%…70%…80%…90%…100%
    Successfully installed “Oracle VM VirtualBox Extension Pack”

    source of this solution: http://marcofalchi.blogspot.com/2011/11/failed-to-install-extension-pack-oracle.html

  13. I have followed the steps 1 by 1 and when i do /etc/init.d/vboxdrv setup or service vboxdrv setup it hangs at ‘Uninstalling old VirtualBox DKMS kernel modules’ and never comes back. I am running Centos6.2 here is more information:

    [root@woods cwoods]# rpm -qa kernel* |sort
    kernel-2.6.32-220.13.1.el6.x86_64
    kernel-2.6.32-220.17.1.el6.x86_64
    kernel-2.6.32-220.7.1.el6.x86_64
    kernel-2.6.32-220.el6.x86_64
    kernel-devel-2.6.32-220.13.1.el6.x86_64
    kernel-devel-2.6.32-220.17.1.el6.x86_64
    kernel-firmware-2.6.32-220.17.1.el6.noarch
    kernel-headers-2.6.32-220.17.1.el6.x86_64
    [root@woods cwoods]# uname -a
    Linux woods.nsi.loc 2.6.32-220.17.1.el6.x86_64 #1 SMP Wed May 16 00:01:37 BST 2012 x86_64 x86_64 x86_64 GNU/Linux
    [root@woods cwoods]#

    Thanks for helping.

    • Turns out I am impatient :-)

      • Hi Chris,

        Nice to hear that you got it working… :D

  14. Thanks for posting great instructions.

    On Fedora 17 there is a less known bug that is causing an error in the vboxdrv setup.

    Basically when dkms is installed, the /usr/sbin/dkms file gets installed as /usr/sbin/dkms.old. So the /etc/init.d/vboxdrv setup gives a ‘Trying to register kernel using dkms – Failed’ message.

    Solution:
    After step 4) above, run this command by logging in as root in terminal windows.

    mv /usr/sbin/dkms.old /usr/sbin/dkms

    Then continue with step 5 onwards.

    BTW – This bug is being fixed right now and there are some patches available on internet.

    Thanks

    • Additional details.

      You can verify if this bug impacts you by running

      ‘which dkms’ after step 4. If the response is ‘no dkms found’

      if everything works correctly, vbox should be listed when you ‘dkms status’ after step 5. The output should look something like this

      vboxhost, 4.1.16, 3.3.7-1.fc17.x86_64, x86_64: installed

      • Hi Vaidya Bala,

        Thank you very much for this information and hopefully this is fixed soon… :)

  15. Excellent instructions
    It was failing to run my VM on FC17 till i installed dkms
    The VirtualBox was running even without dkms but would fail to start VM
    Now after following these instructions it is all good

    Thanks for a great job

  16. Just to say thanks… I was having problems running Virtualbox! Now its working fine :)

  17. Hi there, I am facing a problem with running the command /etc/init.d/vboxdrv setup. See error and logs below:

    [root@AleGodoyNote ~]# /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMSError! Bad return status for module build on kernel: 3.4.0-1.fc17.x86_64 (x86_64)
    Consult /var/lib/dkms/vboxhost/4.1.16/build/make.log for more information.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)
    [root@AleGodoyNote ~]#

    Then the logs:

    [root@AleGodoyNote ~]# cat /var/lib/dkms/vboxhost/4.1.16/build/make.log
    DKMS make.log for vboxhost-4.1.16 for kernel 3.4.0-1.fc17.x86_64 (x86_64)
    Sat Jun 16 22:24:53 BRT 2012
    make: Entering directory `/usr/src/kernels/3.4.0-1.fc17.x86_64′
    /usr/src/kernels/3.4.0-1.fc17.x86_64/arch/x86/Makefile:81: stack protector enabled but no compiler support
    make: gcc: Command not found
    LD /var/lib/dkms/vboxhost/4.1.16/build/built-in.o
    LD /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/built-in.o
    CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/linux/SUPDrv-linux.o
    /bin/sh: gcc: command not found
    make[2]: *** [/var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/linux/SUPDrv-linux.o] Error 127
    make[1]: *** [/var/lib/dkms/vboxhost/4.1.16/build/vboxdrv] Error 2
    make: *** [_module_/var/lib/dkms/vboxhost/4.1.16/build] Error 2
    make: Leaving directory `/usr/src/kernels/3.4.0-1.fc17.x86_64′
    [root@AleGodoyNote ~]#

    And the other log:

    [root@AleGodoyNote ~]# cat /var/log/vbox-install.log
    Uninstalling modules from DKMS
    removing old DKMS module vboxhost version 4.1.16

    ——————————
    Deleting module version: 4.1.16
    completely from the DKMS tree.
    ——————————
    Done.
    Attempting to install using DKMS

    Creating symlink /var/lib/dkms/vboxhost/4.1.16/source ->
    /usr/src/vboxhost-4.1.16

    DKMS: add completed.

    Kernel preparation unnecessary for this kernel. Skipping…

    Building module:
    cleaning build area….
    make KERNELRELEASE=3.4.0-1.fc17.x86_64 -C /lib/modules/3.4.0-1.fc17.x86_64/build M=/var/lib/dkms/vboxhost/4.1.16/build….(bad exit status: 2)
    Failed to install using DKMS, attempting to install without
    make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/3.4.0-1.fc17.x86_64/build modules
    /usr/src/kernels/3.4.0-1.fc17.x86_64/arch/x86/Makefile:81: stack protector enabled but no compiler support
    make[1]: gcc: Command not found
    test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
    echo; \
    echo ” ERROR: Kernel configuration is invalid.”; \
    echo ” include/generated/autoconf.h or include/config/auto.conf are missing.”;\
    echo ” Run ‘make oldconfig && make prepare’ on kernel src to fix it.”; \
    echo; \
    /bin/false)
    mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
    make -f scripts/Makefile.build obj=/tmp/vbox.0
    gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem -I/usr/src/kernels/3.4.0-1.fc17.x86_64/arch/x86/include -Iarch/x86/include/generated -Iinclude -include /usr/src/kernels/3.4.0-1.fc17.x86_64/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -I/lib/modules/3.4.0-1.fc17.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxdrv/ -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -D”KBUILD_STR(s)=#s” -D”KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)” -D”KBUILD_MODNAME=KBUILD_STR(vboxdrv)” -c -o /tmp/vbox.0/linux/SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
    /bin/sh: gcc: command not found
    make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 127
    make[1]: *** [_module_/tmp/vbox.0] Error 2
    make: *** [vboxdrv] Error 2
    [root@AleGodoyNote ~]#

    I read something about enabling hardware -v on BIOS, but I could not find it on my BIOS.. is this error related? Any idea?

    Thanks in advance!

    • Hi

      I looks like you are missing gcc. Please read step #4 and start from there.

      I am not sure what is your host os. If it is Centos or RHEL you have to give 1st and 2nd command of step #4.

      If it is fedora just execute command 2 in step#4.

      If it is 32 bit PAE kernel, execute command 3 in step #4.

      The above instructions work without fail. Just re-read it from the beginning once again and execute them in the order.

      Good luck.

      • True… second command solved my problem… Thank you guys for the help… This was awesome!!!

  18. Thanks a lot , worked without any issues.

  19. i set up the KERN_DIR as directed, but there is nothing in the directory /usr/src/kernels on my load of CENTOS 6. Can you help please

  20. To answer my own question, somehow I missed a step, after some reading I

    yum install gcc kernel-devel kernel-headers

    and everything worked.

    Thank You for an excellent step by step tutorial.

  21. I use to struggle for hours installing this on Fedora! This is great, i am saving this page! Thanks

  22. SOS:
    MyLinux is Fedora17 32bit
    uname -r
    3.5.3-1.fc17.i686.PAE
    I made it as mentioned, but it fail to start.

    yum install VirtualBox-4.1
    ……
    service vboxdrv setup

    Stopping VirtualBox kernel modules [ ok ]
    Uninstalling old VirtualBox DKMS kernel modules [ ok ]
    Trying to register the VirtualBox kernel modules using DKMS[fail]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [fail]
    (Look at /var/log/vbox-install.log to find out what went wrong)

    /var/log/vbox-install.log
    Makefile:172: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again。 stop。

    then I set the KERN_DIR and export it

    KERN_DIR=/usr/src/kernels/`uname -r`
    export KERN_DIR

    pls help me

    • Hi Matthews,

      Could you post output of following commands:

      ls -la /usr/src/kernels/
       
      rpm -qa kernel* |sort
      • I am glad to hear from you. details that I execute orders like blow:

        [root@dds-keda ~]# ls -la /usr/src/kernels/
        总用量 8
        drwxr-xr-x. 2 root root 4096 2月 3 2012 .
        drwxr-xr-x. 4 root root 4096 9月 12 22:21 ..
        [root@dds-keda ~]# rpm -qa kernel* |sort
        kernel-PAE-3.3.4-5.fc17.i686
        kernel-PAE-3.5.3-1.fc17.i686
        [root@dds-keda ~]#

        Pls help me. wait for your reply. thanks a lot.

  23. I am glad to hear from you. details that I execute orders like blow:

    [root@dds-keda ~]# ls -la /usr/src/kernels/
    总用量 8
    drwxr-xr-x. 2 root root 4096 2月 3 2012 .
    drwxr-xr-x. 4 root root 4096 9月 12 22:21 ..
    [root@dds-keda ~]# rpm -qa kernel* |sort
    kernel-PAE-3.3.4-5.fc17.i686
    kernel-PAE-3.5.3-1.fc17.i686
    [root@dds-keda ~]#

    Pls help me. wait for your reply. thanks a lot.

    • Hi Matthews,

      Did you installed following packages on step 4.?

      yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-PAE-devel dkms

      Try to install those again. And then post output of following commands again:

      ls -la /usr/src/kernels/
       
      rpm -qa kernel* |sort
      • You are so nice, I made it. Thanks for your help.
        The other question is how to intall virtualbox in CentOS6 . My company LAN cann’t connect to Internet. Is there Rpm that can be installed without Internet?

        • Hi Matthews,

          You are very welcome!

          You can download VirtualBox RPMs directly from here:
          VirtualBox 4.2.0 32-bit
          VirtualBox 4.2.0 64-bit

          Then you need also all other packages from here:
          CentOS 6 32-bit mirrors
          CentOS 6 64-bit mirrors

          • thanks a lot

          • Hi JR
            I downloaded the file from your link but it gives an error that some files are missing..
            is there any way in which the package is directly downloaded and then it is been automatically installed with whatever packages it need.

  24. stuck at step 3, output versions do not match.

    [root@z3rx1z yum.repos.d]# rpm -qa kernel |sort |tail -n 1
    kernel-3.5.4-2.fc17.x86_64
    [root@z3rx1z yum.repos.d]# uname -r
    3.3.4-5.fc17.x86_64

    any help would be greatly appreciated.

    • stuck at step 3, output versions do not match.

      [root@z3rx1z yum.repos.d]# rpm -qa kernel |sort |tail -n 1
      kernel-3.5.4-2.fc17.x86_64
      [root@z3rx1z yum.repos.d]# uname -r
      3.3.4-5.fc17.x86_64

      any help would be greatly appreciated.

      I also can not run
      service vboxdrv setup

      Stopping VirtualBox kernel modules [ OK ]
      Uninstalling old VirtualBox DKMS kernel modules [ OK ]
      Trying to register the VirtualBox kernel modules using DKMSError! echo
      Your kernel headers for kernel 3.3.4-5.fc17.x86_64 cannot be found at
      /lib/modules/3.3.4-5.fc17.x86_64/build or /lib/modules/3.3.4-5.fc17.x86_64/source.
      [FAILED]
      (Failed, trying without DKMS)
      Recompiling VirtualBox kernel modules [FAILED]
      (Look at /var/log/vbox-install.log to find out what went wrong)

      i may had installed vbox and vmware before everything, and am trying to solve the problem of not being able to create a virtual machine in vbox, and in vmware i can not run i due to missing headers supposedly but i have latest version 3.5 or so and i asks for 3.3 or so

      • Hi sergis,

        Update your system with following command:

        yum update
         
        ## or just kernel ##
        yum update kernel

        And then reboot with kernel-3.5.4:

        reboot

        And then check again and output of commands (on step 3) should match.

        • i attempted this, but recieved this:

          [root@z3rx1z x3rz1x]# yum update kernel
          Loaded plugins: langpacks, presto, refresh-packagekit
          No Packages marked for Update

          • So then you have latest version installed and then just reboot and select 3.5.4 kernel.

  25. Thank you, It works for me on Fedora 17.

  26. I can’t leave the site without saying thanks atleast !!!.

    It was greate, after installing fedora 17 i did not have to search alot to get virtual box installed.

    Thanks Alot :)

    • Hi Yoonas,

      You are very welcome! Excellent to hear that you find useful guides!

  27. #yum update

    File contains no section headers
    file: file:////etc/yum.repos.d/virtualbox.repo, line: 1
    ‘\n’

    What can I do?

    • Hi Tiit,

      Could you post output of following command:

      cat /etc/yum.repos.d/virtualbox.repo
      • I download new virtualbox.repo, and all is OK.

        • Excellent to hear that new repo file fixed your problem.

  28. Thanks! step 4 (dependency packages) did it for me!

    J

  29. Does this work for Fedora 15? And if not, how do I update?

  30. Hi, i’m getting several errors similar to the following below (on fedora16). Is there a way to overcome those without uninstalling the previous version? Please advise.

    Transaction Check Error:
    file /usr/bin/VBox from install of VirtualBox-4.2.4-1.fc16.x86_64 conflicts with file from package VirtualBox-4.1-4.1.22_80657_fedora16-1.x86_64
    file /usr/bin/VBoxTunctl from install of VirtualBox-4.2.4-1.fc16.x86_64 conflicts with file from package VirtualBox-4.1-4.1.22_80657_fedora16-1.x86_64
    ….

    • Hi jo_green29b,

      Why you want to keep VirtualBox-4.1 and VirtualBox-4.2 installed at the same time?

      • Indeed! :) my mistake, what I want to say is: without uninstalling the previous version manually.

        • :)

          Unfortunately there is not way to upgrade VirtualBox directly from 4.1 to 4.2 without removing 4.1 manually, because it’s package with different name.

          So you have to run:

          yum remove VirtualBox-4.1
           
          yum install VirtualBox-4.2

          This shouldn’t affect your virtual machines or configs, but if you want be sure, then backup your virtual machines and configs first. :)

  31. This article saved my life. I spent whole day trying to install VBox properly. The problem was in dependencies. Vbox asked me to run “/etc/init.d/vboxdrv setup” but this command returned error (couldn’t find “make”, god knows why).
    Step “4. Install dependency packages” solved the problem.
    Thank You!!!!!

  32. Hi
    i am not able to install virtual box.
    i am using “yum install VirtualBox-4.2″ this command and i am getting “No package VirtualBox-4.0 available. Nothing to do”.
    Please Help…

    • Hi Nik,

      Could you post output of following commands:

      rpm -qa VirtualBox\*
       
      yum repolist
       
      yum list all |grep VirtualBox
  33. how about rpmfuison way ?
    rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

    yum install VirtualBox

  34. [root@segment-210-214-170-155 ~]# /etc/init.d/vboxdrv setup
    Hi i am getting please help
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMSError! Bad return status for module build on kernel: 3.6.7-4.fc16.x86_64 (x86_64)
    Consult /var/lib/dkms/vboxhost/4.1.16/build/make.log for more information.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)
    Uninstalling modules from DKMS
    removing old DKMS module vboxhost version 4.1.16

    ——————————
    Deleting module version: 4.1.16
    completely from the DKMS tree.
    ——————————
    Done.
    Attempting to install using DKMS

    Creating symlink /var/lib/dkms/vboxhost/4.1.16/source ->
    /usr/src/vboxhost-4.1.16

    DKMS: add completed.

    Kernel preparation unnecessary for this kernel. Skipping…

    Building module:
    cleaning build area….
    make KERNELRELEASE=3.6.7-4.fc16.x86_64 -C /lib/modules/3.6.7-4.fc16.x86_64/build M=/var/lib/dkms/vboxhost/4.1.16/build…..(bad exit status: 2)
    Failed to install using DKMS, attempting to install without
    Makefile:181: *** Error: KERN_DIR does not point to a directory. Stop.

    rpm -qa kernel* |sort
    kernel-3.1.0-7.fc16.x86_64
    kernel-3.6.7-4.fc16.x86_64
    kernel-devel-3.6.7-4.fc16.x86_64
    kernel-headers-3.6.7-4.fc16.x86_64

    uname -a
    Linux segment-210-214-170-155.maa.sify.net 3.6.7-4.fc16.x86_64 #1 SMP Tue Nov 20 20:33:31 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

    • Hi shekhar,

      Could you post output of following command:

      echo $KERN_DIR
  35. it does not work on fedora 14.

    [root@rc-fedora rc]# yum install VirtualBox-4.2
    Loaded plugins: langpacks, presto, refresh-packagekit
    Adding en_US to language list
    Setting up Install Process
    No package VirtualBox-4.2 available.
    Error: Nothing to do
    [root@rc-fedora rc]#

  36. Worked like a charm!
    I swear you can’t go wrong with if !=1 0 guys.
    I would also recomend downloading expansion pack for usb 2.0 ^^

    • Hi markoT,

      Nice to hear that it worked and thank you for compliment. Expansion pack for usb 2.0 is good too, if you need usb support! :)

  37. Your website has quickly become one of my favorite resources… Thank you!

  38. Hello,
    I am stuck on Step 5. I am running Fedora 17 64bit. When I run yum install VirtualBox-4.2 it tells me: yum install VirtualBox-4.2
    Loaded plugins: langpacks, presto, refresh-packagekit
    No package VirtualBox-4.2 available.
    Error: Nothing to do

    I saw two other people had the same problem but never followed up.

    rpm -qa kernel |sort |tail -n 1
    kernel-3.6.11-1.fc17.x86_64
    [root@dbdev ~]# uname -r
    3.6.11-1.fc17.x86_64

    I wasn’t sure which commands in step 4 I was supposed to run. I ran the last two.

    • So I got the install going by running a command I found on another forum.
      yum install dkms

      Once I did that, I was able to run the yum instal VirtualBox-4.2 command successfully

      • Hi Jay,

        If you followed this guide you should have dkms installed after step 4, when you run following command. Last package is just dkms:

        yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms
  39. this is an excellent site…veri nice simple,non distracting interface and good color combo used on ur site….with your permission would like to share few of your posts on my blog with due credit to the original post….thanks

  40. i m getting this message of fedora release conflict

    [root@localhost ~]# rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
    Retrieving http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
    warning: /var/tmp/rpm-tmp.OwJvr9: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
    error: Failed dependencies:
    fedora-release conflicts with epel-release-6-8.noarch

    please help

    • Hi anupam,

      Are you using CentOS 6 or RHEL 6?

      uname -a
       
      lsb_release -a
      • hi JR….fedora 18 using here…regards…

        • So then you don’t need EPEL repo at all.

          From guide:

          CentOS 6/5 and Red Hat (RHEL) 6/5 needs EPEL repository…

  41. Amazing! Thankyou so much you’re so helpful!!

  42. Hello! I’ve followed along all of your instructions and the comments, but still can’t find an answer to my problem: I’m not able to run any of the created virtual machines. I am asked to recompile the vboxdrv module, but when I issue:

    /etc/init.d/vboxdrv setup

    the following error message appears:

    /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules/etc/init.d/vboxdrv: line 304: /usr/share/virtualbox/src/vboxhost/do_dkms: No such file or directory
    [ OK ]
    Trying to register the VirtualBox kernel modules using DKMS/etc/init.d/vboxdrv: line 329: /usr/share/virtualbox/src/vboxhost/do_dkms: No such file or directory
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)

    From the src directory (and downwards) didn’t even existed at the moment of running the program. In turn, the vbox-install.log says:

    etc/init.d/vboxdrv: line 337: /usr/share/virtualbox/src/vboxhost/build_in_tmp: No such file or directory

    I’m using Fedora 18 and my kernel version is:

    3.6.10-4.fc18.x86_64

    • Hi Robert,

      Could you post output of following commands:

      rpm -qa dkms
       
      lsb_release -a
       
      uname -a
  43. hi,
    on installing virtualbox on archlinux, i’getting following,

    WARNING: The vboxdrv kernel module is not loaded. Either there is no module
    available for the current kernel (3.6.11-1-ARCH) or it failed to
    load. Please recompile the kernel module and install it by

    /etc/rc.d/dkms start

    You will not be able to start VMs until this problem is fixed.
    Unknown application – VBox.sh

    output from uname -a

    Linux bridgelinux 3.6.11-1-ARCH #1 SMP PREEMPT Tue Dec 18 12:58:46 CET 2012 i686 GNU/Linux

  44. Thanks a lot fort this concise tutorial !

    Now, I’m looking for a way to avoid the reboting step, in order to install VirtualBox as part of a kickstasrt procedure.

    Is there a way to update yum withouth installing new kernels ?

    • Hi Layus,

      You can exclude kernel updates with following command:

      yum update --exclude=kernel\*
      • Thanks !

        Quite obvious in fact now that I see it.

        Maybe running tenths of VirtualBox instances to test my kickstart file (and then installing and running VirtualBox within…) did not help to my sanity ;-)

        Best regards.

  45. I cant install VirtualBox-4.2. I got this message.

    [root@oc0323586041 Desktop]# yum install Virtualbox-4.2
    Loaded plugins: fastestmirror, ibm-check-lotus-updates, ibm-repository, refresh-
    : packagekit, security, versionlock
    Loading mirror speeds from cached hostfile
    Setting up Install Process
    No package Virtualbox-4.2 available.
    Error: Nothing to do

  46. Hi Defender_1611,

    Check your command it should be:

    yum install VirtualBox-4.2

    Not:

    yum install Virtualbox-4.2
  47. yeah i double check my command its correct I used this command:

    yum install VirtualBox-4.2 but its not working the message is the same im using RHEL6. Look for the message below:

    [root@oc0323586041 ~]# yum install VirtualBox-4.2
    Loaded plugins: fastestmirror, ibm-check-lotus-updates, ibm-repository, refresh-
    : packagekit, security, versionlock
    Loading mirror speeds from cached hostfile
    google-chrome-64bit | 951 B 00:00
    gupc | 2.9 kB 00:00
    rpmforge | 1.9 kB 00:00
    Setting up Install Process
    No package VirtualBox-4.2 available.
    Error: Nothing to do

    • Okay, do you have VirtualBox repo installed and enabled?

      Could you post output of following command:

      yum repolist
  48. Can some one help:

    The vboxdrv kernel module is not loaded. Either there is no module
    available for the current kernel (3.7.6-102.fc17.i686) or it failed to
    load. Reboot the computer or load the kernel module by executing

    ‘/etc/sysconfig/modules/VirtualBox.modules’ (as root)

    You will not be able to start VMs until this problem is fixed.

    ^C
    [root@US-WKS-002 etc]# /etc/sysconfig/modules/VirtualBox.modules
    ERROR: Module vboxdrv not found.
    ERROR: Module vboxnetflt not found.
    ERROR: Module vboxnetadp not found.
    [root@US-WKS-002 etc]# KERN_DIR=/usr/src/kernels/`uname -r`
    [root@US-WKS-002 etc]# rpm -qa kernel |sort |tail -n 1
    kernel-3.7.6-102.fc17.i686
    [root@US-WKS-002 etc]# uname -r
    3.7.6-102.fc17.i686
    [root@US-WKS-002 etc]#

    • Hi Ele,

      I recommend you to update your system using:

      yum update

      Then reboot try to install this again.

  49. Hello JR,

    This is the output. Please see below.

    [root@oc0323586041 ~]# yum repolist
    Loaded plugins: fastestmirror, ibm-check-lotus-updates, ibm-repository, refresh-
    : packagekit, security, versionlock
    Loading mirror speeds from cached hostfile
    repo id repo name status
    KVM-WIN Windows Virtual Client for Linux KVM 20
    RHEL-6-x86_64-openafs Open Client for Linux RHEL 6 x86_64 – OpenAF 14
    RHEL-6-x86_64-rational-linux Open Client for Linux RHEL 6 x86_64 – Ration 4
    RHEL-63-x86_64 Open Client for Linux RHEL 6.3 x86_64 6,670
    RHEL-63-x86_64-ibm-updates Open Client for Linux RHEL 6.3 x86_64 IBM Up 179
    RHEL-63-x86_64-updates Open Client for Linux RHEL 6.3 x86_64 Update 545
    google-chrome-64bit Google Chrome for X86_64 3
    gupc GNU UPC Language Repository http://www.gccupc.org 19+1
    rpmforge RHEL 6Workstation – RPMforge.net – dag 4,458
    repolist: 11,912

    • Looks like you don’t have VirtualBox repo, so recheck step 2.

  50. Hi,

    Host – Fedora 18 desktop 64bit
    Virtualbox – 4.2.6

    I encountered problem here;

    # /etc/init.d/vboxdrv setup
    -bash: /etc/init.d/vboxdrv: No such file or directory

    # service vboxdrv setup
    Redirecting to /bin/systemctl setup vboxdrv.service
    Unknown operation ‘setup’.

    # /sbin/service vboxdrv setup
    Redirecting to /bin/systemctl setup vboxdrv.service
    Unknown operation ‘setup’.

    pls help. Thanks

Leave a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Trackbacks/Pingbacks