Yeah same problem here. The 17 kernel that I installed came from hardy-updates. But Virtualbox doesn't yet have an updated kernel module. Guess I'll be booting into 16 until that time...
Yeah same problem here. The 17 kernel that I installed came from hardy-updates. But Virtualbox doesn't yet have an updated kernel module. Guess I'll be booting into 16 until that time...
Kernel module may also be obtained by compiling it from sources (that exist in the repository - search for "virtualbox" in synaptic). For me that worked fine.
but how do i compile it then?
I got the same problem after today's kernel update. Reinstall virtualbox solved it.
That's a good one. Although, i wish they'd make sure it works before releasing the kernel to the public.
Edit: Disclaimer: I haven't actually tried the proposed solution, but it looks like a good one. A temporary fix until the real one is released. I went with the "boot into the old kernel"-option, which is alot easier.
Last edited by ubuntism; May 27th, 2008 at 07:44 PM.
Shows over. It works now. Just upgrade from the repository. Thanks ubuntu people. Whoever you all are, thanks.
Er... I didn't read the VirtualBox error message that carefully, but it did also say that I should add my user to the virtualbox user group (which I hadn't done, since this was a fresh install and I didn't pay attention). So of course THAT was why I needed to log out and back in...
Once I applied the kernal driver update, added myself to the virtualbox user group, and logged out and back in, my virtual machine worked again.
I had the 64bit deb installed and got this same error this morning after the upgrade. I just ran
Seemed to clear the problem up.Code:sudo dpkg-reconfigure virtualbox
Bookmarks