DISQUS

Exsecrabilus · 1 year ago

Wow. What a coincidence. I just tried VirtualBox yesterday and and had that problem. I forgot about it, and come here, and here's the solution! :)

Vadi · 1 year ago

Yes, that fix worked for me

Tony · 1 year ago

Excellent post! You fixed my problem before I even realized I needed it :-)

Anonymous · 1 year ago

Worked like a charm!

GreySim · 1 year ago

The good news is that DKMS is supposed to fix this in Intrepid. I foolishly run Intrepid as my main system and I use Virtual Box 2 from the Ubuntu repos, and every time I get a kernel update it automatically updates the VBox modules. I haven't had any problems with spawning sessions, and I know I've had at least two kernel updates since installing VBox.

Jonathan · 1 year ago

Having to repeat this process with future kernel upgrades can be prevented by installing the dkms package in Synaptic.

See posts by frank and me (jblackhall):
http://www.virtualbox.org/ticket/2421

Ramesh · 1 year ago

Man u read my mind.. I have updated 2.6.24-21 from 2.6.24.19. Major issue is that my Cisco Vpn no longer works. then I thought of starting Virtual Box then connect VPN through xp. it has right there on swapping session.. No luck and clue from googling. Then switched back to 2.6.24.19. VPN and virtual Box are happy.

Any clues on VPN . I did have patch and reinstalled ( compiled with latest kernel )

will there be an issue once u compile VirBox with 2.6.24.21 and going back to 2.6.24.19

I am regular reader of you blog.. I really enjoy it .. Keep up the good work.

Cheers
Ramesh

LaPeGa · 1 year ago

I fix it doing this:
$ sudo dpkg-reconfigure virtualbox-2.0

dmitry · 1 year ago

It works!
Thank you! Accurately and useful ...

Anonymous · 1 year ago

Thanks!!!!

Max · 1 year ago

Thanks for the tip. Worked perfectly.

Anonymous · 1 year ago

Thank you! This worked perfectly. My machine took 20-30 seconds to recompile the kernel.

Anonymous · 1 year ago

Thanks for the fix. This was driving me nuts. :)

TheBinary · 1 year ago

Thank you! It worked perfect! Nice!

Hugh · 1 year ago

This is why I like this blog so much. The posts are always so topical! No point searching Google anymore for problems. Just wait for Tombuntu to post a fix! ;-)

Cosmin · 1 year ago

thank you,
I had this problem and your solution worked ;)

Nelson Delgado · 1 year ago

Ran into the problem after yesterdays kernel upgrade...
Works like a charm! thanks!

ischnura · 1 year ago

Just in time!

I was having this same problem.

Thanks for the info it helped a lot :)

Pete · 1 year ago

Nice one. Simple fix to a frustrating problem post a major set of 8.04 updates.

Cheers

Anonymous · 1 year ago

I had no idea this problem was caused by the kernel update. It now works. Thank you!!

Ollie · 1 year ago

Thanks for the post. Worked perfectly.

cefleet · 1 year ago

Hey thanks your a lifesaver. MY work depends on Vbox and i saw this this morning and was about to prepare myself for a long day, but thanks to you my day has gotten a little better.

Alex · 1 year ago

Thank you very much Tom !!!

Anonymous · 1 year ago

thx

Owdy · 1 year ago

Thanks, that worked in openSUSE 11.1 too!

TheEmulator · 1 year ago

Gracias
Era lo que buscaba :)

Anonymous · 1 year ago

Man, can play my Rhapsody again. I appreciate your input and effort

mindjuju · 1 year ago

thx!

Anonymous · 1 year ago

Worked for me too. Thank you!

Anonymous · 1 year ago

thank you very verymuch.

Henry · 1 year ago

I doesn't work for me. I got an error:

Cannot change owner vboxusers for device /dev/vboxdrv


----------------------
* Stopping VirtualBox kernel module * done.
* Removing old VirtualBox kernel module * done.
* Recompiling VirtualBox kernel module * done.
* Starting VirtualBox kernel module
* Cannot change owner vboxusers for device /dev/vboxdrv

Tom · 1 year ago

Henry:
Maybe the permissions on /dev/vboxdrv have been messed up. I'd try something like this to change the owner to root and the group to vboxusers (how it is on my system):
sudo chown root:vboxusers /dev/vboxdrv

fishears · 1 year ago

THANK YOU FOR THIS FIX.
I knew you had to re-configure vmware for new kernels but I didn't know this applied to vbox as well. Shame on them for not putting a useful message on screen when this happens...
Still... it IS free, isn't it, so what the hey?!

PhoenixP3K · 1 year ago

So glad I came across that tip! Simple, direct and effective. Just the way I like them!

Jesper · 1 year ago

The reason why this happens is because you got a kernel update. If you install a new kernel, you must have new kernel modules, including a new kernel module for VirtualBox.

The fix described here rebuilds the VirtualBox kernel module for the new kernel.

Note that you don't get a new VirtualBox kernel module automatically, because you installed VirtualBox from a *.deb package yourself, and not from the Ubuntu repository.

TioLucas · 1 year ago

Desde Argentina
Muchas gracias amigo, It works!

khelll · 1 year ago

It worked perfectly,Thanks alot!

John John · 1 year ago

Many Thanks from Greece for that!!!!

You are great!!!

qbl · 1 year ago

thanks a lot. you saved my day!

Anonymous · 1 year ago

Excellent tip, thanks so much for posting! I installed VBox from *.deb for the USB support, and forgot completely that I needed to add kernel modules. And it was the first match that google found when searching for the error message. Very handy!

lu · 1 year ago

It worked fine for my Ubuntu 8.04 2.6.24-22-generic
Linux kernel. There is a method to install VirtualBox
so that this (good) workaround is no more necessary ?
Thank You and Best regards.

Anonymous · 1 year ago

It works!Thanks

dimeotane · 11 months ago

Thank you for your post! I had work to do immediately in virtualbox, but I had no idea how to fix it. Thank goodness I had access to wireless to google for the solution.

Anonymous · 11 months ago

didnt work for me. just said [FAILED] check /var/installlog but there's no such file...