How to Install Latest VirtualBox 6.0 in Linux

Best Affordable Linux and WordPress Services For Your Business
Outsource Your Linux and WordPress Project and Get it Promptly Completed Remotely and Delivered Online.

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.45/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Ravi Saive

I am Ravi Saive, creator of TecMint. A Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux. Follow Me: Twitter, Facebook and Google+

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

134 Responses

  1. Hermouche says:

    For those who still have a problem when they launch the command:

    $ sudo /sbin/vboxconfig

    I’ve solved my problem by disabling the “secure boot” from the bios (i am using the standard Unified Extensible Firmware Interface “UEFI”)

    My machine:
    CentOS Linux release 7.3.1611 (Core)
    Linux AP-amphi.ensm.intranet 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  2. Sevki Akdemir says:

    File: /var/log/vbox-install.log;

    Makefile:185: *** Error: unable to find the sources of your current Linux kernel. 
    Specify KERN_DIR= and run Make again. Stop.
    make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /usr/src/kernels/2.6.32-042stab116.1/ -j4 modules
    make[1]: warning: -jN forced in submake: disabling jobserver mode.
    test -e include/linux/autoconf.h -a -e include/config/auto.conf || (            \
            echo;                                                           \
            echo "  ERROR: Kernel configuration is invalid.";               \
            echo "         include/linux/autoconf.h or include/config/auto.conf are missing.";      \
            echo "         Run 'make oldconfig && make prepare' on kernel src to fix it.";  \
            echo;                                                           \

    Can any body help ?

    • Ravi Saive says:


      Could you show me the output of the following commands:

      # rpm -qa kernel* | sort
      # uname -mr
      # echo $KERN_DIR

      I suggest you to first update the system and then try to install Virtualbox.

  3. sayanthan says:

    i currently used Ubuntu 16.04 (xenial).
    i try to update then i got flowing warning ..
    “W: GPG error: xenial InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF
    W: The repository ‘ xenial InRelease’ is not signed.
    N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
    N: See apt-secure(8) manpage for repository creation and user configuration details.'”

    after install time
    WARNING: The following packages cannot be authenticated!
    Install these packages without verification? [y/N]

    what to do now?
    is i continue? is this better or not?

    • Ravi Saive says:


      First you need to remove old Virtualbox keys before doing a upgarde, here is how to remove the old keys:

      $ sudo apt-key list

      Find the offending key (something like “virtualbox”, after “pub”, xxx/KEYHERE) and do:

      $ sudo apt-key del VirtualBox-KEYHERE

      Then follow the instructions as described in this article..

  4. lance-link says:

    I used the above procedure to install VirtualBox 5.1 in a Fedora host and a Windows 7 guest, however, I have to run # /usr/lib/virtualbox/ setup each time after reboot/shutdown inorder to get any devices to appear in VB > Settings > USB > USB Device Filters. How can I make the change permanent so I don’t have to run # /usr/lib/virtualbox/ all the time?

    I posted this question a few minutes ago but the email address was wrong.

  5. lance-link says:

    I followed the installation process for VirtualBox in a Fedora 24 host and a Windows 7 guest. Everything worked fine, but I have to run # /usr/lib/virtualbox/ setup each time after a reboot/shutdown inorder to get any listings in Settings > USB > USB Device Filters.

    How can I make the USB Filter choices permanent so i don’t have to run # /usr/lib/virtualbox/



    I try to install virtualbox 5 on centos 7 but he gave the header problem then I install it but still having the issue ,plus what should I do

    # yum install kernel-devel

    • Ravi Saive says:


      Could you share the exactly what error message is giving by Virtualbox? so that it will help us to better identify the problem..

  7. waleed says:

    i get this error when run virtualbox

    Qt FATAL: This application failed to start because it could not find or load the Qt platform plugin “xcb”.

    Available platform plugins are: xcb.

    Reinstalling the application may fix this problem.
    Aborted (core dumped)

    • Ravi Saive says:


      It seems xcb libraries are not installed on the system, to install just run the following command will fix the error:

      $ sudo aptitude install libdouble-conversion1 libxcb-render-util0 libxcb-image0 libxcb-icccm4 libxcb-randr0 libxcb-keysyms1 libxcb-xkb1 libxkbcommon-x11-0
      • Steve says:

        I have the same problem, I checked this list and installed the first item which was the only one missing and still get this error, I am running on Linux Mint 17.1

        • Ravi Saive says:


          I suggest you to install all missing xcb related packages and see, if it solves the error..

          • Steve says:

            The only package that was missing was libdouble-conversion1 and I have already installed it. So all the packages listed above are installed but it still gives me this error.

          • Steve says:

            I found this on another site, if I run this
            P=/usr/lib/virtualbox; sudo LD_LIBRARY_PATH=$P:$P/plugins/platforms $P/VirtualBox
            in a terminal then Virtualbox opens like it should and it works, so doesn’t seem to be missing component.

          • Ravi Saive says:


            Thanks for sharing the tip, I hope it will help other users, who are facing similar issue….

    • Nenad Cimerman says:

      First of all, many thanks for this very useful guide!

      However, in my case (CentOS 5.11) with the current VirtualBox Version 5.1.2, I ran into a problem which blocked virtualbox when started, so I could not use it at all:
      $ virtualbox
      Qt FATAL: This application failed to start because it could not find or load the Qt platform plugin “xcb”.

      Available platform plugins are: xcb.

      Reinstalling the application may fix this problem.

      After some research, I discovered, that the required “xcb” libraries are installed in /usr/lib/virtualbox and /usr/lib/virtualbox/plugins.

      So the solution is quite simple. As “root” (or using sudo) user do the following two steps:
      1. create a new file containing the two paths mentioned above
      # cd /etc/
      # vi virtualbox-5.1.2.conf
      2. Update system wide configuration of “ldd”
      # /sbin/ldconfig

      Hope this helps some people to overcome this missing peace in the installation procedure of the VirtualBox package.
      Have fun!


  8. Peter Schneider says:

    Although six weeks are gone since your question, just a hint:
    I just installed VirtualBox-5 on my Fedora-21 box. The script ‘’ did the job for me:
    # /usr/lib/virtualbox/ setup

    • Ravi Saive says:


      Thanks for the tip, hope it will other users.. Keep sharing such hints with us and keep connected to Tecmint…

    • Dandu Rajeev says:

      Hi Peter,
      I have tried this. But got this error:

      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 4.5.7-200.fc23.x86_64 cannot be found at
      /lib/modules/4.5.7-200.fc23.x86_64/build or /lib/modules/4.5.7-200.fc23.x86_64/source.
      (Failed, trying without DKMS)
      Recompiling VirtualBox kernel modules [FAILED]
      (Look at /var/log/vbox-install.log to find out what went wrong)

      Any help will be appreciated.

      • Ravi Saive says:


        It seems me to like a Kernel header problem, you should install kernel-headers using:

        # yum install kernel-devel
  9. simon says:

    sorry for my poor English… I fail to install on Centos 7 at start stem, neither of these commands succeed:
    # /etc/init.d/vboxdrv setup
    # service vboxdrv setup


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

    service vboxdrv setup
    The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl.

    I found no error in /var/log/vbox-install.log

    Any hints ? Thanks !

    • Ravi Saive says:

      Have you correctly installed and enabled VirtualBox repository under /etc/yum.repos.d/ directory in your CentOS 7?

      • Dandu Rajeev says:

        similar issue for me. I installed virtualbox repo in /etc/yum.repos.d/. I am using Fedora 23. I badly need VirtualBox. Please give me some solution to make it work. Thanks!

        • John Cook says:

          It appears there is a minor error in this guide. The suggested options for a RHEL/CentOS 7 host (or Fedora 19-24 hosts) are actually only suitable for RHEL/CentOS 5/6 hosts (or Fedora 16-18 hosts). Here is the change I made to the author’s procedure that allowed me to get VirtualBox 5.1 working on my CentOS 7 host:

          /usr/lib/virtualbox/ setup
          usermod -a -G vboxusers user_name

          NOTE: Replace “user_name” with an actual user name.

          I was able to otherwise follow this guide and just replace the portion concerning rebuilding the kernel modules with what I supplied above.


          • Ravi Saive says:


            Thanks a ton for pointing out, we’ve included the instructions as suggested, hope it will help other users who are facing similar issues with latest version of CentOS/RHEL and Fedora..

  10. AJ says:

    What’s the deal with the 32bit only guests?

Got something to say? Join the discussion.

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.