I have installed virtualbox 4.3 onto my OPENSUSE64-13.1 installation. everything seems to have went fine until I try to create a virtual server. Everytime after creating with the NEW command i try to start and I receive this error "Kernel driver not installed (rc=-1908)" I have tried to do what it said to no avail and have tried many googled solutions. Please help! here is all the info I have:
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
'/etc/init.d/vboxdrv setup'
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
Failed to open a session for the virtual machine Ultimate UBUNTU 42.
The virtual machine 'Ultimate UBUNTU 42' has terminated unexpectedly during startup with exit code 1.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
/etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules done
Uninstalling old VirtualBox DKMS kernel modules done
Trying to register the VirtualBox kernel modules using DKMS
done
Starting VirtualBox kernel modules done
"
Kernel driver not installed (rc=-1908)
Re: Kernel driver not installed (rc=-1908)
Have you tried to install the DKMS? you will need that installed.
Re: Kernel driver not installed (rc=-1908)
Same issue here using Ubuntu 13.10.
Error message when I try to start a virtual machine:
I've found suggestion on other websites to reinstall virtualbox-dkms:
sudo apt-get remove virtualbox-dkms
sudo apt-get install virtualbox-dkms
Error message when I try to start a virtual machine:
Other error window:Échec de l'ouverture de session pour la machine virtuelle Windows 7.
The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1.
Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : Machine
Interface : IMachine {22781af3-1c96-4126-9edf-67a020e0e858}
When I type the suggested command line (/etc/init.d/vboxdrv setup):VirtualBox - Error In suplibOsinit
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
'/etc/init.d/vboxdrv setup'
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
I tried this command line : sudo /etc/init.d/virtualbox restartsudo: /etc/init.d/vboxdrv: command not found
dkms and virtualbox-dkms packages are installed.* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found [fail]
I've found suggestion on other websites to reinstall virtualbox-dkms:
sudo apt-get remove virtualbox-dkms
sudo apt-get install virtualbox-dkms
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found [fail]
invoke-rc.d: initscript virtualbox, action "restart" failed.
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Kernel driver not installed (rc=-1908)
maybe this will help. Install VirtualBox on OpenSUSE 13.1
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
Re: Kernel driver not installed (rc=-1908)
I have the same issue with OSX 10.9.4 and VirtuaBox 4.3.12
-
- Posts: 1
- Joined: 31. Aug 2014, 22:34
Re: Kernel driver not installed (rc=-1908)
These instructions worked for me guys. Encountered said error with Linux Mint 17, this fixed it.Scaler wrote:Same issue here using Ubuntu 13.10.
Error message when I try to start a virtual machine:Other error window:Échec de l'ouverture de session pour la machine virtuelle Windows 7.
The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1.
Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : Machine
Interface : IMachine {22781af3-1c96-4126-9edf-67a020e0e858}When I type the suggested command line (/etc/init.d/vboxdrv setup):VirtualBox - Error In suplibOsinit
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
'/etc/init.d/vboxdrv setup'
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.I tried this command line : sudo /etc/init.d/virtualbox restartsudo: /etc/init.d/vboxdrv: command not founddkms and virtualbox-dkms packages are installed.* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found [fail]
I've found suggestion on other websites to reinstall virtualbox-dkms:
sudo apt-get remove virtualbox-dkms
sudo apt-get install virtualbox-dkms
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found [fail]
invoke-rc.d: initscript virtualbox, action "restart" failed.
-
- Posts: 4
- Joined: 24. Apr 2015, 06:15
Re: Kernel driver not installed (rc=-1908)
SOLUTION
Took me a long time to solve this issue. Had this problem with vBox across 2 distros (Ubuntu and Arch).
I had dkms and all the modules already installed and compiled into my kernel, yet I still got a module related error message when I tried to run a vBox virtual machine.
If your vBox GUI starts without a hitch but get an error telling you to install the VBoxDrv kernel module (or any other modules) when you try to run a virtual machine, your problems are not related to installing the modules into your kernel but ACTIVATING THEM in modprobe which the module installation script fails to do.
To load a module manually (such as vboxdrv), open a terminal prompt and put in :
sudo modprobe vboxdrv
if your error message is telling you that your missing another module, be sure to activate it as well.
If you Virtual Machine runs after that without giving you an error message, you've found the solution. Then you can activate the vboxdrv module permanently by going to /etc/modules-load.d/ (or whatever .d directory your modprobe uses) and making a .conf file within it (such as vbox.conf). In the .conf file, put in the names of the vbox kernel modules you want to add, such as: vboxdrv and optionally vboxnetadp, vboxnetflt and vboxpci. If you don't know what they do, see the excerpt below that I took out of vBox's wiki. Save the .conf file and reboot
From Vbox's wiki:
vboxnetadp and vboxnetflt are both needed when you intend to use the "Host-only networking" feature. More precisely, vboxnetadp is needed to create the host interface in the VirtualBox global preferences, and vboxnetflt is needed to launch a virtual machine using that network interface.
vboxpci is needed when your virtual machine needs to pass through a PCI device on your host.
Note: If the VirtualBox kernel modules were loaded in the kernel while you updated the modules, you need to reload them manually to use the new updated version. To do it, run vboxreload as root.
Took me a long time to solve this issue. Had this problem with vBox across 2 distros (Ubuntu and Arch).
I had dkms and all the modules already installed and compiled into my kernel, yet I still got a module related error message when I tried to run a vBox virtual machine.
If your vBox GUI starts without a hitch but get an error telling you to install the VBoxDrv kernel module (or any other modules) when you try to run a virtual machine, your problems are not related to installing the modules into your kernel but ACTIVATING THEM in modprobe which the module installation script fails to do.
To load a module manually (such as vboxdrv), open a terminal prompt and put in :
sudo modprobe vboxdrv
if your error message is telling you that your missing another module, be sure to activate it as well.
If you Virtual Machine runs after that without giving you an error message, you've found the solution. Then you can activate the vboxdrv module permanently by going to /etc/modules-load.d/ (or whatever .d directory your modprobe uses) and making a .conf file within it (such as vbox.conf). In the .conf file, put in the names of the vbox kernel modules you want to add, such as: vboxdrv and optionally vboxnetadp, vboxnetflt and vboxpci. If you don't know what they do, see the excerpt below that I took out of vBox's wiki. Save the .conf file and reboot
From Vbox's wiki:
vboxnetadp and vboxnetflt are both needed when you intend to use the "Host-only networking" feature. More precisely, vboxnetadp is needed to create the host interface in the VirtualBox global preferences, and vboxnetflt is needed to launch a virtual machine using that network interface.
vboxpci is needed when your virtual machine needs to pass through a PCI device on your host.
Note: If the VirtualBox kernel modules were loaded in the kernel while you updated the modules, you need to reload them manually to use the new updated version. To do it, run vboxreload as root.
-
- Posts: 1
- Joined: 4. Jul 2016, 13:55
Re: Kernel driver not installed (rc=-1908)
The code did the magic, thanks! However, I dont get the part about activating vboxdrv module permanently. Sorry, I'm an amateur.
Last edited by socratis on 10. Jan 2017, 21:50, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Reason: Removed unnecessary verbatim quote of the whole previous message.