Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Kernel driver not installed (rc=-1908)

  1. #1
    Join Date
    Mar 2016
    Location
    Tunisia
    Posts
    4

    Default Kernel driver not installed (rc=-1908)

    Virtualbox stopped working after recent tumbleweed update.
    launching any vm results in showing error

    <<
    Kernel driver not installed (rc=-1908)

    The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

    '/sbin/vboxconfig'

    as root.

    where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

    It seems not founding /sbin/vboxconfig to recompile drivers ...
    >>

    Here is my system
    rogue:/home/vpc # uname -a
    Linux rogue 4.10.12-1-default #1 SMP PREEMPT Fri Apr 21 11:50:25 UTC 2017 (3043bd9) x86_64 x86_64 x86_64 GNU/Linux

    An when i run the vbconfig, le file is not found :

    rogue:/home/vpc # /sbin/vboxconfig
    bash: /sbin/vboxconfig: No such file or directory

    My distrib version is here after

    rogue:/home/vpc # cat /etc/*-release
    LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
    DISTRIB_ID="openSUSE Tumbleweed"
    DISTRIB_RELEASE="20170213"
    DISTRIB_CODENAME=""
    DISTRIB_DESCRIPTION="openSUSE Tumbleweed"
    NAME="openSUSE Tumbleweed"
    # VERSION="20170420"
    ID=opensuse
    ID_LIKE="suse"
    VERSION_ID="20170420"
    PRETTY_NAME="openSUSE Tumbleweed"
    ANSI_COLOR="0;32"
    CPE_NAME="cpe:/opensuse:tumbleweed:20170420"
    BUG_REPORT_URL="https://bugs.opensuse.org"
    HOME_URL="https://www.opensuse.org/"


    I checked for the module here after :

    rogue:/home/vpc # chkconfig vboxdrv
    vboxdrv on
    rogue:/home/vpc # modprobe vboxdrv
    modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.10.12-1-default
    rogue:/home/vpc # ls -lah /sbin/vboxconfig
    ls: cannot access '/sbin/vboxconfig': No such file or directory
    rogue:/home/vpc # ls -lah /sbin/ | grep -i vbox
    rogue:/home/vpc #
    rogue:/home/vpc # ls -lah /dev/vboxdrv
    ls: cannot access '/dev/vboxdrv': No such file or directory
    rogue:/home/vpc #
    rogue:/home/vpc # modprobe vboxdrv
    modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.10.12-1-default
    rogue:/home/vpc # rpm -qa 'kernel*' '[Vv]irtual[Bb]ox*'
    virtualbox-5.1.18-2.3.x86_64
    kernel-default-4.10.12-1.2.x86_64
    virtualbox-host-kmp-default-5.1.18_k4.10.12_1-2.3.x86_64
    kernel-default-4.10.10-1.1.x86_64
    virtualbox-qt-5.1.18-2.3.x86_64
    kernel-firmware-20170404-1.1.noarch
    rogue:/home/vpc # systemctl status vboxdrv
    vboxdrv.service - LSB: VirtualBox Linux module
    Loaded: loaded (/etc/init.d/vboxdrv; generated; vendor preset: disabled)
    Active: failed (Result: exit-code) since Tue 2017-05-02 12:16:44 CET; 3min 29s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 7486 ExecStart=/etc/init.d/vboxdrv start (code=exited, status=1/FAILURE)

    May 02 12:16:44 rogue systemd[1]: Starting LSB: VirtualBox Linux module...
    May 02 12:16:44 rogue vboxdrv[7486]: vboxdrv.sh: Starting VirtualBox services.
    May 02 12:16:44 rogue vboxdrv[7486]: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
    May 02 12:16:44 rogue systemd[1]: vboxdrv.service: Control process exited, code=exited status=1
    May 02 12:16:44 rogue systemd[1]: Failed to start LSB: VirtualBox Linux module.
    May 02 12:16:44 rogue systemd[1]: vboxdrv.service: Unit entered failed state.
    May 02 12:16:44 rogue systemd[1]: vboxdrv.service: Failed with result 'exit-code'.


    Nothing seems to make vbox run properly...
    Any suggestion please?


  2. #2
    Join Date
    Jan 2016
    Location
    Manchester, UK
    Posts
    279

    Default Re: Kernel driver not installed (rc=-1908)

    Maybe the following command could bring it back,

    `sudo modprobe vboxdrv`

    Sorry for the formatting because I am using a phone.
    openSUSE Tumbleweed (usually the latest snapshot) w/ KDE Plasma 5

  3. #3

    Default Re: Kernel driver not installed (rc=-1908)

    Same basic problem here. Tumbleweed current as of a few minutes ago. I uninstalled and re-installed all the virtualbox packages, and the error changed to what I present here.

    Error when I try to start a VM:
    Failed to open/create the internal network 'HostInterfaceNetworking-enp0s31f6' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

    Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

    One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/sbin/vboxconfig' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND).



    Result Code:
    NS_ERROR_FAILURE (0x80004005)
    Component:
    ConsoleWrap
    Interface:
    IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


    $ uname -a
    Linux HQ-slmbp.us.ara.com 4.10.12-1-default #1 SMP PREEMPT Fri Apr 21 11:50:25 UTC 2017 (3043bd9) x86_64 x86_64 x86_64 GNU/Linux
    # locate vboxconfig
    # echo $?
    1
    # cat /etc/os-release
    NAME="openSUSE Tumbleweed"
    # VERSION="20170429"
    ID=opensuse
    ID_LIKE="suse"
    VERSION_ID="20170429"
    PRETTY_NAME="openSUSE Tumbleweed"
    ANSI_COLOR="0;32"
    CPE_NAME="cpe:/opensuse:tumbleweed:20170429"
    BUG_REPORT_URL="https://bugs.opensuse.org"
    HOME_URL="https://www.opensuse.org/"
    # lsmod | grep vb
    vboxdrv 458752 0
    # rpm -qa 'kernel*' '[Vv]irtual[Bb]ox*'
    kernel-default-4.10.10-1.2.x86_64
    kernel-macros-4.10.12-1.2.noarch
    kernel-firmware-20170404-1.1.noarch
    kernel-source-4.10.12-1.2.noarch
    kernel-source-4.10.10-1.2.noarch
    kernel-default-devel-4.10.12-1.2.x86_64
    virtualbox-qt-5.1.18-2.3.x86_64
    kernel-default-devel-4.10.10-1.2.x86_64
    virtualbox-host-kmp-default-5.1.18_k4.10.12_1-2.3.x86_64
    kernel-default-4.10.12-1.2.x86_64
    kernel-devel-4.10.12-1.2.noarch
    kernel-devel-4.10.12-1.1.noarch
    kernel-source-4.10.12-1.1.noarch
    kernel-syms-4.10.12-1.1.x86_64
    kernel-syms-4.10.12-1.2.x86_64
    virtualbox-5.1.18-2.3.x86_64
    kernel-devel-4.10.10-1.2.noarch
    # systemctl status vboxdrv
    Unit vboxdrv.service could not be found.

    From journalctl:
    May 02 14:58:36 host.example.com kernel: vboxdrv: ffffffffc1344020 VMMR0.r0
    May 02 14:58:36 host.example.com kernel: vboxdrv: ffffffffc0246020 VBoxDDR0.r0

  4. #4

    Default Re: Kernel driver not installed (rc=-1908)

    Additional info.

    After a reboot, I get the same error as the original poster:
    Kernel driver not installed (rc=-1908)


    If I do
    modprobe vboxdrv
    then the problem changes to the one I give above.

  5. #5

    Default Re: Kernel driver not installed (rc=-1908)

    And, finally, changing from bridged to NAT network allows the VM to boot.

  6. #6

    Default Re: Kernel driver not installed (rc=-1908)

    I have got same problems as above. Changing bridget to NAT doesn't work for me. Is this is a problem with VB configuration or I should wait for a VB update?

    Code:
    
    uname -a
    Linux linux-86z6 4.10.13-1-default #1 SMP PREEMPT Thu Apr 27 12:23:31 UTC 2017 (e5d11ce) x86_64 x86_64 x86_64 GNU/Linux
    

  7. #7

    Default Re: Kernel driver not installed (rc=-1908)

    Quote Originally Posted by GarryMoveOut View Post
    I have got same problems as above.
    And what problems exactly?
    The error message mentioned in the title only says that the kernel driver could not be loaded.
    The reasons for it may be various.

    There is currently a problem in Tumbleweed that old-style sysvinit scripts (like virtualbox still uses) are not started automatically on boot.
    Manually running "systemctl start vboxdrv.service" (or loading the kernel modules manually) should make VB work.
    Creating a symlink /etc/rc.d/ that points to /etc/init.d/ should fix that problem in general, and will be re-introduced in one of the next Tumbleweed updates AFAIK.

    Another reason may be that the kernel modules are either not installed, or only installed for the wrong kernel.
    Try to reinstall the package virtualbox-host-kmp-default:
    Code:
    sudo zypper in -f virtualbox-host-kmp-default
    Or are you talking about this error message?
    Failed to open/create the internal network 'HostInterfaceNetworking-enp0s31f6' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

    Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
    Is this is a problem with VB configuration or I should wait for a VB update?
    Depends on what exactly the reason for *your* problem is...

    The next VB update will fix the two problems I mentioned above though:
    - it will use a native systemd service file instead of the sysvinit script
    - it will rebuild the kernel modules for the running kernel automatically if they are not found

    Code:
    
    uname -a
    Linux linux-86z6 4.10.13-1-default #1 SMP PREEMPT Thu Apr 27 12:23:31 UTC 2017 (e5d11ce) x86_64 x86_64 x86_64 GNU/Linux
    
    Ok, but it would be also interesting what exact virtualbox packages you have installed, i.e. whether they match your running kernel...
    Code:
    rpm -qa | grep -i virtualbox
    Though I strongly suspect that your problem is covered by what I wrote above.

  8. #8

    Default Re: Kernel driver not installed (rc=-1908)

    Details about my error which occurs when I want to start one of my VB machine

    Kernel driver not installed (rc=-1908)

    The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

    '/sbin/vboxconfig'

    as root.


    where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

    The virtual machine 'Debian87' has terminated unexpectedly during startup with exit code 1 (0x1).
    Kod wyniku (RC): NS_ERROR_FAILURE (0x80004005)
    Komponent: MachineWrap
    Interfejs: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
    Code:
    rpm -qa | grep -i virtualbox
    virtualbox-host-kmp-default-5.1.18_k4.10.13_1-2.5.x86_64
    virtualbox-5.1.18-2.5.x86_64
    virtualbox-qt-5.1.18-2.5.x86_64
    
    
    If there is going update I will rather wait for it and test. Maybe my problem will be solved. I am not in rush.

  9. #9

    Default Re: Kernel driver not installed (rc=-1908)

    Quote Originally Posted by GarryMoveOut View Post
    Code:
    rpm -qa | grep -i virtualbox
    virtualbox-host-kmp-default-5.1.18_k4.10.13_1-2.5.x86_64
    virtualbox-5.1.18-2.5.x86_64
    virtualbox-qt-5.1.18-2.5.x86_64
    
    
    Looks ok.

    What does "rpm -V virtualbox-host-kmp-default" say?
    If it reports missing files, reinstall the package as mentioned.
    (The ENOENT in your error message seems to indicate that the files are in fact missing)

    And "systemctl start vboxdrv.service" should load the kernel modules and "fix" virtualbox.
    Because of that other "bug" (missing /etc/rc.d/ symlink), this is not done automatically at boot currently.

    But yeah, both problems should be fixed by an upcoming update...
    Both the virtualbox and the insserv-compat update have been accepted to Factory already and should be in the next snapshot I suppose.
    (the insserv-compat update will re-add the missing /etc/rc.d/ symlink and therefore fix running sysvinit scripts automatically on boot, but that won't even be necessary any more for virtualbox then)

  10. #10

    Default Re: Kernel driver not installed (rc=-1908)

    I checked your command "rpm -V virtualbox-host-kmp-default" and it does't returned anything.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •