error when trying to start virtual machine

dwsdad · Post by **dwsdad** » 25. Aug 2008, 16:08

I've installed Virtual Box on a Kubuntu server succesfully, but I'm getting an error when I try to start up a partition created for XP. It's telling me the user must be added to vboxuser group, which I did and then restarted the Linux server. After the restart, I'm still getting the error. Ideas?

Post by **Sasquatch** » 25. Aug 2008, 16:17

Did you read the full error message? It clearly states that you have to log off from the Host before any changes take effect.

dwsdad · Post by **dwsdad** » 25. Aug 2008, 16:46

Yep. I rebooted the host box just to make sure. And I double checked the group to make sure the user was in it.

Post by **Sasquatch** » 25. Aug 2008, 17:41

Could you give some more information? Read the Forum Posting Guide to help you give the proper information we need to help you. Also, what version did you install (OSE or PUEL)?

dwsdad · Post by **dwsdad** » 26. Aug 2008, 01:46

Here's the error I get when trying to start my virtual machine:

Code: Select all

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 {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

I believe I'm running OSE. I installed it using the Adept Manager on an x86 PC. I am not running a 64 bit machine.

Let me know what else I need to post and I'll do my best to put it out here.

Post by **TerryE** » 26. Aug 2008, 05:16

You really need to read the error and perform some diagnostic analysis, rather than relying on us for miracle answers. Basically the module src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp pukes this error out if it fails to open /dev/vboxdrv read-write. Since this is owned by a different user the rw access is through its vboxusers group ownership.

So does /dev/vboxdrv exit? Have you done an ls -l on it? If not the device may not be starting for some reason. Did you have any errors during the VBox install?

shaddow · Post by **shaddow** » 26. Aug 2008, 12:24

I have the same problem using Mandriva linux.

The installation RPM did not created directory /dev/vboxdrv.
should i create it manually? what should by the directory permissions?

I had no screen errors during installation, are the errors dumped into a log file during installation?

Thank you.

João Veríssimo

dwsdad · Post by **dwsdad** » 26. Aug 2008, 13:50

I have vboxdrv. It's owned by root with a group of vboxusers.

paulsiu · Post by **paulsiu** » 26. Aug 2008, 19:09

You probably need to be added to the vboxuser group as instructed in the user manual.

dwsdad · Post by **dwsdad** » 26. Aug 2008, 19:19

I am in the vboxusers group and I have rebooted the host machine, not just logged off, to make sure the new account worked right. Here's the entry from /etc/group:

vboxusers:

doug,dwsdad

Post by **Sasquatch** » 26. Aug 2008, 20:54

Have you tried to reinstall the whole VB package? Be sure to get every package you can that has to do with VB. In case of the OSE, install VB-OSE, it's HOST Kernel Module for the kernel you run (so if you run the -generic kernel, install the module for generic and not -i686). Be sure that the Module is for the same version of kernel as you have running. I've seen the new kernel module for kernel 2.6.24-20 in the Ubuntu repo, but that kernel version is not released as of yet.

If you fail to get the OSE running, remove every package from it, go to the download page on the VB site (www.virtualbox.org) and download the PUEL version. Before you install VB, be sure that you have the proper packages installed to build kernel modules. Those are the Linux Headers, GCC, DKMS and preferrably Module Assistent, though I'm not sure about the last one. Now see if it works properly. Every VM you created will be accessible by the PUEL version too, and won't be removed when removing VB.

dwsdad · Post by **dwsdad** » 27. Aug 2008, 01:54

I went into Adept Manager and found where I had somehow loaded Sun Virtual Box, not OSE, so I uninstalled that version and installed Virtualbox -OSE and VirtualBox Guest Modules for -2.6.24-19-generic (after doing a uname -a to find my kernel version).

Virtualbox-OSE installs fine, ie, no errors and places a link the System Menu, and it WAS working until it told me the driver was a different version. Duh, yeah, from the Sun version. So I uninstalled everything again - this time making sure I deleted /etc/vbox and .Virtualbox from my home directory. Once again, it installs fine with no errors, BUT now when I go to launch it from the menu, it just doesn't load. No errors. Nothing on the screen.

I have unloaded and removed everything again and will try VMWare, or just for grins, I may load Sun Virtualbox again and see what happens.

dwsdad · Post by **dwsdad** » 27. Aug 2008, 03:05

UPDATE:

VMWare successfully installed, but just like VirtualBox, it would not load. I went back and the downloaded version I have of Virtualbox - 1.6.2-31466_Ubuntu_hardy_i386.deb and installed it. This is the Sun version, and it loaded fine. I had to set a few persmissions and build a module, but I can now load XP. So far, the only error I'm getting is something about the USB drivers. I'll have to play with that and see if the USB ports even work, and if I have network from my virtual server through the host. XP is still installing right now.

Post by **Sasquatch** » 27. Aug 2008, 11:39

For USB, see the Help docs of Ubuntu. There is described nicely how to get it working. We will pick the USB part from it some day and put it here too, with tested results. If you search here, you will find a nice howto too.

dwsdad · Post by **dwsdad** » 27. Aug 2008, 13:51

Thanks. I'll take a look at that. The network is working and the sound, so I think all I lack would be the USB. I'll play with that tonight and see if I can get it working.