Page 1 of 1
-1911 (VERR_VM_DRIVER_OPEN_ERROR)
Posted: 26. Jun 2008, 12:08
by Demosthenes2k8
Whenever I try to open my VM, I get this error:
VirtualBox kernel driver cannot be opened.
VBox status code: -1911 (VERR_VM_DRIVER_OPEN_ERROR).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
I am running Ubuntu 8.04 and the guest is tinyXP_Rev05.iso
Has anyone gotten this error before? How do I fix it?
Posted: 26. Jun 2008, 14:49
by Sasquatch
Are you a member of the vboxusers group? It looks like it you aren't. In a terminal, type the following:
Enter your password and look at the end of the file for a line that says 'vboxusers'. At the end of that line, add your own username, save the file using CTRL+O, close nano with CTRL+X and log out and back in. Now you should be able to use VB. This is described in the manual, FAQ and during setup.
Posted: 26. Jun 2008, 15:23
by Demosthenes2k8
nope...
VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
Now I get this error.
Posted: 26. Jun 2008, 16:38
by Sasquatch
And what if you execute that command, sudo /etc/init.d/vboxdrv/setup?
Posted: 26. Jun 2008, 18:49
by Demosthenes2k8
command not found
Posted: 26. Jun 2008, 18:57
by Sasquatch
Do'h, I meant 'sudo /etc/init.d/vboxdrv setup'.
It should be created during setup, including the kernel driver. That is, if you have the kernel headers to create kernel modules.
Posted: 27. Jun 2008, 18:53
by Demosthenes2k8
nope, still "command not found"
Posted: 27. Jun 2008, 19:51
by stefan.becker
Delete this crappy Version and install newest Version from the VBOX Homepage.