VirtualBox 4.3.14 on Fedora 20/19, CentOS/Red Hat (RHEL) 6.5/5.10

virtualbox-logo-smallOracle 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
  • Windows 8
  • Windows 8.1
  • DOS
  • Linux (2.4, 2.6, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11)
  • Solaris
  • OpenSolaris
  • OpenBSD

This guide shows howto install VirtualBox 4.3 (currently 4.3.14) on Fedora 20/19/18/17/16/15, CentOS 6.5/6.4/6.3/6.2/6.1/6/5.10, Red Hat (RHEL) 6.5/6.4/6.3/6.2/6.1/6/5.10. 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 20/19/18/17/16/15/14/13/12 users
## CentOS 6.5/6.4/6.3/6.2/6.1/6/5.10 and Red Hat (RHEL) 6.5/6.4/6.3/6.2/6.1/6/5.10 users

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 -V |tail -n 1
uname -r

Note: If you got kernel update or run older kernel than newest installed then 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
## CentOS 5 and RHEL 5 ##
rpm -Uvh
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.3 (currently 4.3.14)

yum install VirtualBox-4.3

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:



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 ##
## CentOS and Red Hat (RHEL) example ##
## 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!


  1. Hi.

    Nice howto.

    I am having the same problem as some of the people above. have tried to look trought your awnsers but I can’t fins what I have done wrong/missing.

    Have a newly installed fedora 20 (less than 1 day old).

    My problem:

    [root@localhost yum.repos.d]# /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 DKMS[ OK ]
    Starting VirtualBox kernel modules [MISSLYCKADES]
    (modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)

    (MISSLYCKADES means failed in Swedish).

    Some output that you have requested before from others:

    [root@localhost yum.repos.d]# uname -a
    Linux localhost.localdomain 3.13.9-200.fc20.x86_64 #1 SMP Fri Apr 4 12:13:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

    [root@localhost yum.repos.d]# rpm -qa kernel |sort -V |tail -n 1

    [root@localhost yum.repos.d]# yum list installed |grep kernel |sort
    abrt-addon-kerneloops.x86_64 2.2.0-1.fc20 @updates
    kernel-devel.x86_64 3.13.9-200.fc20 @updates
    kernel-headers.x86_64 3.13.9-200.fc20 @updates
    kernel-modules-extra.x86_64 3.11.10-301.fc20 @koji-override-0/$releasever
    kernel-modules-extra.x86_64 3.13.9-200.fc20 @updates
    kernel.x86_64 3.11.10-301.fc20 @koji-override-0/$releasever
    kernel.x86_64 3.13.9-200.fc20 @updates

    dmesg and cpu info:


    Thanks in advanced.


    • Hi Krister,

      Thank you for nice initial info.

      Unfortunately I can’t download your dmesg.txt, because I can’t run that .exe and I don’t have premium account.

      Everything else looks very good.

      You can also try following as root and post output here:

      modprobe vboxdrv
  2. Hi.

    Thanks for getting back so soon.

    Funny that you cant download the dmesg.txt. Can’t you press the to link “download dmesg.txt”, something like that I have the Swedish translation. If you need it let me know than I will find some other way beside posting it here.

    The output that you requested:
    [root@localhost ~]# modprobe vboxdrv
    modprobe: ERROR: could not insert ‘vboxdrv': Required key not available

    • Hi Krister,

      Actually I don’t need that dmesg file anymore. Reason why modprobe vboxdrv fails is secure boot. You can check my earlier comment about VirtualBox and secure boot.

      So go to bios and disable secure boot and then run setup again. If you still have problems, please let me know.

  3. Works perfectly, thank you.


    • Excellent to hear that you got it working!

  4. fedora has a new kernel, i got error: Your kernel headers for kernel 3.13.9-200.fc20.x86_64 cannot be found at
    /lib/modules/3.13.9-200.fc20.x86_64/build or /lib/modules/3.13.9-200.fc20.x86_64/source.

    • Hi Fabse,

      Did you updated also kernel-headers and kernel-devel packages?

      Could you post output of following commands:

      uname -a
      rpm -qa kernel\* |sort -V
  5. There is a much easier way to install programs to newest versions of Fedora by using “Yumex”

    • Hi cito,

      First you have to of course install Yumex. And quick look shows that the VirtualBox is not even available if you install just Yumex or am I wrong?

      It’s nice that there is alternatives, like Yumex, but for me yum and PackageKit is enough…

  6. No package VirtualBox-4.3 available. Any ideas?

  7. if you run into erros during /etc/init.d/vboxdrv setup

    then do

    uname -r

    to get the kernel version. and do

    yum install kernel-devel-{ouput from uname -r}

    you should be all set after that..atleast for me on F19

    • Thanks Praveen – that was the ticket for my KERN_DIR errors. That and installing GCC compiler

  8. I have a linode VPS and I’m getting this error:

    Trying to register the VirtualBox kernel modules using DKMSError! echo
    Your kernel headers for kernel 3.14.4-x86_64-linode40 cannot be found at
    /lib/modules/3.14.4-x86_64-linode40/build or /lib/modules/3.14.4-x86_64-linode40/source.
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]

    any way for me to get those kernel modules manually installed?

    • Hi jcy,

      All (old discussions) what I found from the Internet about Linode kernel packages was that, they do not ship any kernel-headers or kernel-devel packages. But their xen kernels are vanilla kernels and it’s possible to build those packages yourself. I really can’t say that they use vanilla kernels nowadays.

      Linode have excellent support, so maybe you could ask directly from Linode support if they have kernel-headers and kernel-devel packages available for your kernel.

  9. Hi,

    I followed your tutorial for installing virtualbox on my centos machine.(it is the first link on google search).

    After importing my vm I saw that it allows me to allocate only 4GB ram from the 32 GB I have on my host system. The EPEL repositories you have mentioned are both for 32 bit hosts, but they works on 64 bit hosts anyways. Since most of the systems now are 64 bit, and many people will come to this link and follow the installation instructions as such, it would be awesome if you could modify this page and add instructions for 64bit hosts wherever applicable.

    • Hi Akshay,

      This EPEL package is noarch package so it doesn’t make any difference if you install x86_64 package, try following:

      wget -O epel-i386.rpm
      wget -O epel-x86_64.rpm
      md5sum epel-*


      2cd0ae668a585a14e07c2ea4f264d79b  epel-i386.rpm
      2cd0ae668a585a14e07c2ea4f264d79b  epel-x86_64.rpm

      Exactly same package. Arch is determined in repo file. That’s why I have mentioned only 32-bit url, but you can of course download exactly same file from x86_64 url too (if you want). So this guide is totally 64-bit compatible.

      I just tested this on 64-bit Fedora and I can allocate more than 4GB ram.

      Could you first post output of following command:

      uname -a
  10. Next time be sure to use

  11. Virtualbox only run as root
    But can’t run as user.

    Message :

    Failed to create the VirtualBox COM object.

    The application will now terminate.

    Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007)

    • Hi Ruben,

      Could you first change normal user and post output of following commnand:


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>


  1. Howto Install VirtualBox (with yum) on Fedora 12, CentOS 5.4, Red … | Just linux! - [...] Go here to read the rest:  Howto Install VirtualBox (with yum) on Fedora 12, CentOS 5.4, Red … [...]
  2. Upgrade to Fedora 13 from Fedora 12 with Preupgrade | if not true then false - [...] 10 on Fedora 13Install Sun Java (JDK, JRE) on Fedora 13Install Adobe AIR 1.5 and 2 on Fedora 13Install …
  3. Fedora NetInstall (Net Install) with gPXE and BFO ( | if not true then false - [...] on Fedora 13Install Adobe AIR 1.5 and 2 on Fedora 13Install Adobe (Acrobat PDF) Reader on Fedora 13Install VirtualBox …
  4. Install VirtualBox Guest Additions on Fedora 13, CentOS 5.5, Red Hat (RHEL) 6 | If Not True Then False - [...] 6. Reboot guest systemrebootThen VirtualBox Guest Additions install is ready.Check also:Install VirtualBox (with yum) on Fedora, CentOS, Red Hat …
  5. CentOS 5.5 Netinstall – Network Installation | If Not True Then False - [...] 5.5Install Sun/Oracle Java (JDK, JRE) 6 on CentOS 5.5Install Adobe AIR 1.5 and 2 on CentOS 5.5Install VirtualBox (with …
  6. Como instalar o VirtualBox no Fedora « - [...] if !1 0 Compartilhe: fedora, linux, máquina virtual, virtualbox, [...]
  7. Delicious Bookmarks for March 22nd through March 23rd « Lâmôlabs - [...] Install VirtualBox 4.0.4 on Fedora 14/13, CentOS/Red Hat (RHEL) 5.5/6 – March 22nd ( tags: virtualbox fedora centos …
  8. Install VirtualBox 4.0.4 on Fedora 14/13, CentOS/Red Hat (RHEL) 5.5/6 « Записки Миханика. - [...] Install VirtualBox 4.0.4 on Fedora 14/13, CentOS/Red Hat (RHEL) 5.5/6. Рубрика: C других сайтов, Linux, Новости …
  9. How To Install VirtualBox In Fedora | JF Agno Freelance Web Consultant and Web Developer in Davao Philippines - [...] Thats it simple right here is the original source click here [...]
  10. Installing VirtualBox on our Linux Clients » CS SysAdmin - [...] Reference: [...]