Solution to "Kernel driver not installed (rc = -1908)" in Virtualbox (Arch)

As many of you know, VirtualBox is a software virtualization for x86 architectures, originally created by the German company innotek GmbH. It is currently developed by Oracle Corporation as part of its family of virtualization products. Through this application it is possible install additional operating systems, within another operating system, each with its own virtual environment.

When installing VirtualBox on Arch Linux and trying to run it I ran into the following error: "Kernel driver not installed (rc = -1908)"


What we have to do to solve this error is to execute the following commands in a terminal:

sudo modprobe vboxdrv

This loads the kernel module vboxdrv. For this module to load when the system starts, the following file must be edited:

sudo nano /etc/rc.conf

and add vboxdrv in section:

MODULES = (vboxdrv)

Now you should be able to run VirtualBox without any problem, at least that worked for me.


Leave a Comment

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

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   Jearel alcantara said

    Hey friend, remember to also add the modules for network adapters, which are vboxnetadp and vboxnetflt, useful for remote connections to that VM

  2.   David Salazar said

    I had already read it in one of the forums, but thanks for the information, it was a bit annoying bug.

  3.   Courage said

    It happened to me months ago and until I just saw your article I have not found the solution

  4.   Let's use Linux said

    I'm glad it worked!
    Cheers! Paul.

  5.   Let's use Linux said

    Very good! Thanks for sharing!
    Cheers! Paul.

  6.   Javier said

    It is not a bug it is part of the configuration in arch it is in the wiki but since we do not like to read we think it is a problem, remember that it is arch and not Ubuntu, not everything is done

  7.   Nick flows said

    The good thing about not loading the module automatically is that we don't waste resources, since we only use it when we run VirtualBox. I use a script to start the module.

    #! / Bin / bash
    # vboxnetflt
    gksudo modprobe -a vboxdrv &&
    VirtualBox –startvm "UUID_MaquinaVirtual" &&
    #VirtualBox &
    exit

  8.   Let's use Linux said

    You're welcome!
    A hug! Paul.

  9.   Carlos said

    Thanks a lot. It is never too much to save these tips in case it happens to you in the future.
    Greetings.

  10.   Anurus Croador chilensis said

    Like Christian vilches, the solution didn't work for me either, adding virtualbox-dkms like cesar alonso didn't solve it either, I'm using Linux mint 12 KDE, however when using Linux Mint Debian edition I had no problem, I suppose it is because it is activated by default the vboxdrv module and this one of course exists in the kernel and not in mint KDE

  11.   Let's use Linux said

    In Mint you may need to install the DKMS package first. Cheers! Paul.

  12.   Let's use Linux said

    Before doing so, you may have to run: /etc/init.d/vboxdrv setup
    On May 5, 2012 20:21 pm, Pablo Castagnino wrote:

  13.   Croador Anuro said

    in the end I cut my losses and reinstalled Linux Mint debian edition and issue solved 🙂

  14.   Let's use Linux said

    Haha! It seems perfect!
    A hug! Paul.

  15.   Stephen DB said

    Great !! I had tried with 3 different installations of VBox, and with two different XP and nothing, until I apply what you say

  16.   Richard Henry said

    Thanks man, it worked for me! 🙂

  17.   Victor De Vierna Friend said

    Hello! I have ubuntu 12.04, I have tried many pages with many different solutions, and I get the error in all of them.
    What I can do? I think »» that I may have a problem with my version of the linux kernel? It has just been updated but until now I had not used it so I do not know if that is the cause. How can I reinstall my kernel? thanks 😛

  18.   Let's use Linux said

    You're welcome!
    A hug! Paul.

  19.   JP said

    Hello! I'm new to crunchbang 11 (I'm coming from ubuntu, fedora, and linux mint)

    I got this error 1 day after installing xp and using it as normal at work.

    I fixed it using only the first command that you indicate "sudo modprobe vboxdrv"

    Thank you!

  20.   christian vilches said

    : ~ $ sudo modprobe vboxdrv
    FATAL: Module vboxdrv not found.

  21.   Let's use Linux said

    How weird ... what version of the kernel are you using?
    Have you already installed virtual box?
    Cheers! Paul.

  22.   Cesar Alonso said

    The same happened to me. I have Ubuntu 11.10 and maybe that's it ...

  23.   Cesar Alonso said

    Hmm. I have solved it with
    sudo apt-get remove virtualbox-dkms
    sudo apt-get install virtualbox-dkms

  24.   Saul said

    Thank you very much it served me without any problem.

  25.   Cristian castro said

    modprobe vboxdrv

    this was the one that worked for me for arch

  26.   JGuacaran133 said

    Excellent, it worked for me without problems too! Thank you…

  27.   maxi said

    Thank you very much teacher, very useful. 😀

    1.    let's use linux said

      You're welcome, dad! I send you a hug! Paul.

  28.   Juan Carlos said

    [carlos @ Carlos-PC ~] $ sudo modprobe vboxdrv
    [sudo] password for Carlos:
    modprobe: FATAL: Module vboxdrv not found.
    [carlos @ Carlos-PC ~] $

  29.   Juan Carlos said

    Greetings to all, does anyone have a solution please, the terminal gives me this error:
    [carlos @ Carlos-PC ~] $ sudo modprobe vboxdrv
    [sudo] password for Carlos:
    modprobe: FATAL: Module vboxdrv not found.
    [carlos @ Carlos-PC ~] $

    1.    let's use linux said

      Hi Juan Carlos!
      You have probably already figured out the solution. Anyway, I share it in case the same thing happens to someone else.
      The error came out because you probably updated the kernel and did not restart. Likewise, sometimes when you update the kernel and then plug in a usb device (let's say memory) it doesn't detect it well. The solution: restart the computer. Then everything will work out like a charm. And remember: whenever you update the kernel, don't forget to reboot the machine.
      A hug! Paul.

      1.    Juan Carlos said

        Thank you very much for answering me, the truth is that the issue brought me quite a fly and if of course when restarting it was solved, but it is also appreciated that you inform me of where the failure was.
        A small request if you are so kind and please could you make when you could a small tutorial on how to install PacketTracer in Archilinux, because I have not been able to solve it and I was reading the wiki but I followed the steps and nothing, so If you are so kind and have some time and you feel like it please I would appreciate it very much, thank you and a hug from Spain, Tarragona 🙂.

  30.   Gilberto said

    Hi I can't run VirtualBox and I did what you indicate, but it won't allow me, if you help me, I have Ubunto 12.04 LTS

  31.   Richard Rodriguez said

    I have the same error, I have oracle linux6, I have tried everything, but nothing has come out, I have even reinstalled several times, someone will have some advice for this, I have been with this problem for several days

    1.    yukiteru said

      With Oracle Linux, why don't you call for service? Although if you want to revive it by your own means, it is not a bad idea to recompile the VirtualBox module for the kernel version you have, although for that you will have to check what tools OL has to do this task, in Debian for example DKMS is used, and does everything automatically.

      1.    Gilberto Esteban Cano Tapia said

        I do not have the number nor do I know what the technical service is

  32.   Gilberto Esteban Cano Tapia said

    The truth is that I have been trying to solve the problem for a long time, I have done everything they say in the forums, but I have not been able to make the virtua box work, and that is because of my work I need windows and I have not been able to and I need it if someone can you help I would appreciate it.

  33.   Michael Caro said

    The indications in the post did not help me so I looked and found this solution that worked for me:

    Section: 2.3.2. The VirtualBox kernel module

    Link: https://www.virtualbox.org/manual/ch02.html

  34.   Norberto said

    I did as many but I could not solve it until I read Miguel Caro's post, thank you very much Miguel.

    That way I was able to run virtualbox on Archlinux.

    Greetings.

  35.   Hector said

    thanks! your help helped me!

  36.   static said

    This solution still works, it is momentary, every time I restart the system I have to retype this solution, is there a definitive one?

    1.    let's use linux said

      The second part of the post does not work for you? You have to load the vboxdrv module when starting the system.

  37.   David said

    You are my savior * _ * haha ​​thanks ^ _ ^ but if you can, could you explain to me how do you know that?

    1.    elian said

      look how to add you ??

  38.   Gerard said

    In my case, that I use Manjaro, I found that the virtualbox version was incompatible with my Kernel and I was getting this (identical) error. I installed the dkms and did several more tests but nothing worked, until I found another solution:

    It turns out that I had installed virtualbox using "sudo pacman -S virtualbox" and this installed by default the package "linux310-virtualbox-host-modules", when the one I need is the "linux44-virtualbox-host-modules", since that number is the one that corresponds to the version of my Kernel, 4.4.

    This is how I fixed it, in case someone else runs into that problem. And of course I permanently removed the packages from the dkms. After installing / uninstalling the computer must be restarted.

    Regards!

  39.   Mariana nunes said

    Good! Mijo I get an error! when I go to Terminal <> and put 'sudo modprobe vboxdrv' it tells me FATAL: module "vboxdrv" not found

    WHAT DO I DO !!! ????

  40.   RF said

    Hello everyone ... I had the same problem with VB (version 5.1.22) in Ubuntu 16.04 and I spent a while reading and testing, until I solved the issue as follows:

    First of all, it is recommended to close Virtual Box before using the terminal.

    Once closed I wrote the following line in the terminal: sudo apt-get install gcc make
    Then as root (sudo -i) I wrote the following line: sudo -i / sbin / vboxconfig

    And ready !!! after this, I was able to use VB without any problem.

    I hope they serve.
    Greetings.

  41.   jason said

    I get an error! when I go to the Terminal and put 'sudo modprobe vboxdrv' it tells me FATAL: module "vboxdrv" not found
    and from there I don't know what to do?

  42.   jaffeth said

    hello I have the problem that does not let me use sudo modprobe vboxdrv tells me that modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
    how can I solve that

  43.   AHR said

    For those who could not solve this problem with this post. I have published the solution that worked for me in this link:

    https://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur/1199583#1199583

    I hope to be of help.
    Greetings.

  44.   Anais said

    Tried many solutions and this was the one that worked for me. Thank you!