Virtual box error NS_ERROR_FAILURE (0x80004005)

[burntresistor]

the problem is I can't get into virtual box. I get the same error I did what the error reccomeneded which i attached below. After I reinstalled dkms I went into etc/init.d and clicked on the dkms auto installer file which didn't run it terminal wouldn't open same with vboxdrv,there isn't one with actual setup in the title. terminal didn't want to run the file.



Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {13420cbb-175a-4456-85d0-301126dfdec7}


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. Re-setup the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

[Locutus_of_Borg]

Just download the Linux installer from Sun's website

you have mismatched kernel modules, the installer from Sun will recompile the modules for you.

[merlinus]

Same thing happened to me after installing some updates. I checked and DKMS was already installed.

But running the command prefaced by sudo fixed everything.

sudo /etc/init.d/vboxdrv setup

[theGlitch]

I just want to bump this with a thank you... I've been banging my head about this one for a week

[essius]

Same thing happened to me after installing some updates. I checked and DKMS was already installed.

But running the command prefaced by sudo fixed everything.

sudo /etc/init.d/vboxdrv setup

Thanks alot !

[thiefy]

hi, i got that error also.
all you have to do (at least for me) was run virtualbox as root.


simply gksudo VirtualBox &


that's it.
it wants to run as root i guess...
if you start it from the menu - i get that error - saying that the virtual machines are not accessible.

oh, and notice the caps in that command. they are needed...

[granade]

Same thing happened to me after installing some updates. I checked and DKMS was already installed.

But running the command prefaced by sudo fixed everything.

sudo /etc/init.d/vboxdrv setup

Bump for thanks!

[dakaltty]

while installing the kernel i got this error message..

Makefile:152: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.


How can i resolve it?

[Astrals]

I am having the same problem.

i'm using ubuntu-9.10-alternate-amd64 from fresh install did the system updates, setup the system to my needs, installed virtualbox-3.1_3.1.0-55467_Ubuntu_karmic_amd64.deb (latest version) from sun (for extra functionality) and it worked great last night, then turned my system on again about 12 hours later (did not install anything and no updates available) and vbox now coming up with the same error i have tried the above with the same error, also tried complete removal and reinstall also with no luck.


Error:
Failed to create the VirtualBox COM object.
The application will now terminate.
Start tag expected, '<' not found.
Location: '/home/xxxx/.VirtualBox/VirtualBox.xml', line 1 (0), column 1.
/home/vbox/vbox-3.1.0/src/VBox/Main/VirtualBoxImpl.cpp[420] (nsresult VirtualBox::init()).


Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {2158464a-f706-414b-a8c4-fb589dfc6b62}




"xxxx"=my username
Any help with this will be very much appreciated, hopefully this might help someone out as well.



EDIT:
I found a solution for this.
In your home folder /home/xxxx/.VirtualBox the file VirtualBox.xml became corrupted so delete it (when you restart virtualbox you will have to re-register).
After that go to virtualbox menu for Virtual Media Manager and add the xxxx.vmdk image to it.
Next step add a new OS for virtualbox and select the first (for me xp) then select for Boot Hard Disk use existing hard disk and select the one you added for media manager.
There your done vbox is now working with your virtual hard disk before the crash and you don't loose anything.

My next step was back in my .Virtualbox folder i copied the 3 files (compreg.dat, VirtualBox.xml and xpti.dat) to .xxxx (copy) in the same folder (just in case this happens again).
The last step was to make another virtualbox snapshot.

I hope this helps you out as well.

[lilo624]

Thank you Astrals, this did the trick for me. Have been looking for a solution for weeks. But makes me wonder why the "VirtualBox.xml" became corrupt in the first place?

Once again, thanks for posting. Your are a life saver!