Hey.
I have a vm with Kali Linux installed on my Ubuntu 15.10, which I used for a while now, and worked perfectly until now.
One time when I lunched it, it didn't lunch and the following massage appeared:
"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. 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.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. "
So I executed the commend as shown, but no change in the results occurred. I have restarted and then tried again, but it didn't help.
When I click on "Details" on the error massage, this is what I see:
"The virtual machine 'Kali Linux' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}"
I don't know what to do, and would be happy if you could help me.
Thanks.
Error while lunching Kali Linux VM on Ubuntu 15.10.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Error while lunching Kali Linux VM on Ubuntu 15.10.
What happens if you run the following in the hosts terminal
Code: Select all
sudo rcvboxdrv setupRe: Error while lunching Kali Linux VM on Ubuntu 15.10.
Yep, it worked, thanks allot!Perryg wrote:What happens if you run the following in the hosts terminalCode: Select all
sudo rcvboxdrv setup
May I ask what was the problem?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Error while lunching Kali Linux VM on Ubuntu 15.10.
I believe it has to do with recent changes to the initv/systemd and the fact that the hint is not updated, but that is only a guess. I do know this command I sent you usually fixes the issue.