virtualbox.org

unable to load vbox to an active session receiving a verr_vm_ driver not installed
message please recompile the kernel but then issueing the the command to recompile the permissions aren't granted

Sorry, not this way. If you need help, then make understable posts with infos and full sentences.

Else look Astro-TV or use a Crystal Bowl to solve your problems.

aronm3 wrote:unable to load vbox to an active session receiving a verr_vm_ driver not installed
message please recompile the kernel but then issueing the the command to recompile the permissions aren't granted

Are you in the vboxusers group? You have to be, else you can't access the /dev/vboxdrv file.

Hi,
I have downloaded and installed VB 2.1.0 on my Ubuntu 8.04. When I first started it with the command virtualbox, a message told me to add my user to the vboxusers group, thing that I have done. I relogged in and now I do not get the message in the console anymore, but the VM still does not start...

what can be wrong? what can I check?

thanks in advance

Ste

Does the VM say "aborted"? If so, any errors in the VirtualBox machine log (CTRL+L) would be useful. (Don't post the entire log on the forum!)

Stéphane

Hi Stephane,

I get an error popup saying:

Failed to start the virtual machine <name>

The VirtualBox kernel driver is not accessible to the current user. Make sure that the user has write permissions for /dev/vboxdrv by adding them to the vboxusers groups. You will need to logout for the change to take effect..
VBox status code: -1909 (VERR_VM_DRIVER_NOT_ACCESSIBLE).


Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

Well Stephano, that error is pretty obvious as to how to fix it.

Hi, thanks for your reply, but it is actually not that much obvious, at least to me.... please read again the original post. I am already in the vboxusers group (otherwise I would not have posted my problem ).

ste@derfel2:~$ id
uid=1000(ste) gid=1000(ste) groups=115(admin),124(vboxusers),1000(ste)

Any additional hint?
Thanks in advance,
Ste

Check the permissions on the device. Do an 'ls -l /dev/vboxdrv' to check the permissions. Change if needed with chown.

Already tried

ste@derfel2:~$ ls -la /dev/vboxdrv
crw-rw-rw- 1 root vboxusers 10, 61 2008-12-20 16:41 /dev/vboxdrv

it is very weird, isn't it?

ste

Did you try to complete remove, including the config (your VMs will be kept), VB, reboot and then install it again? I know that I had some kind of permissions error or related when I upgraded from 1.6.6 to 2.0.0 and it's possible that it's the same from 2.0.x to 2.1.0.

Thanks for keeping looking into it.

I have not removed completely the version I have with synaptic. I looked in .config and there is no virtualbox directory.

Shall I check anything else?

ste

For the rectords, this is the content of the log...


ste@derfel2:~$ cat .VirtualBox/Machines/Windows\ XP/Logs/VBox.log
00:00:05.270 VirtualBox 1.5.6_OSE r28240 linux.x86 (Apr 9 2008 01:30:09) release log
00:00:05.270 Log opened 2008-12-22T08:05:01.149781000Z
00:00:05.270 ERROR [COM]: aRC=0x80004005 aIID={1dea5c4b-0753-4193-b909-22330f64ec45} aComponent={Console} aText={The VirtualBox kernel driver is not accessible to the current user. Make sure that the user has write permissions for /dev/vboxdrv by adding them to the vboxusers groups. You will need to logout for the change to take effect..
00:00:05.270 VBox status code: -1909 (VERR_VM_DRIVER_NOT_ACCESSIBLE)} aPreserve=false
00:00:05.296 Power up failed (vrc=VERR_VM_DRIVER_NOT_ACCESSIBLE, hrc=0x80004005)

Thanks to my friend Gary, under the threat of switching to Fedora the issue is now solved. And I believe I now understand what I have done.

I initially installed VB 2.1 and saw that it created a launch command VirtualBox... I though, there must be virtualbox either, being a linux system... I ran it and did not tell me the command was not available... it told me "The program 'virtualbox' is currently not installed. You can install it by typing:

sudo apt-get install virtualbox-ose

...
Ok, I am dumb, but I thought that was just a starting script (end in ose, which is not the name of the product...). Instead installed the whole package, most probably corrupting the installation.

We reinstalled everything from scratch and now it works...

Ste