VirtualBox fails to start any virtual machine after update to 2.6.24-22-generic

Bug #303475 reported by Roshan George
This bug report is a duplicate of:  Bug #303199: virtualbox-ose-modules broken AGAIN. Edit Remove
4
Affects Status Importance Assigned to Milestone
virtualbox-ose (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

VirtualBox fails with the error that the vboxdrv kernel module was not loaded. The exact error is in the attachment. This occurred immediately after updating to the latest kernel version of Ubuntu 8.04.1: 2.6.24-22-generic. VirtualBox works fine if I start my installation of Ubuntu with the 2.6.24-21-generic kernel.

Revision history for this message
Roshan George (roshan-george) wrote :
Revision history for this message
Roshan George (roshan-george) wrote :

If I may venture a reason for this problem it is that the virtualbox-ose-modules package has no version for this kernel version. Is it possible to package the module for the newer kernel? I would have reported this somewhere to request for packaging but I don't know how.

Thank you

Revision history for this message
LumpyCustard (orangelumpycustard) wrote :

If I understand correctly, Hardy and below do not have the DKMS capability made by Dell. Intrepid offers this (2.6.27) but clearly you shouldn't have upgrade to 8.10 to use VB. I only offer this as an option.

Revision history for this message
Roshan George (roshan-george) wrote :

I'm sorry, I don't understand what you're saying. What is DKMS?

VirtualBox is working fine in the 2.6.21 kernel.

Revision history for this message
Daniel Hahler (blueyed) wrote :

I'm marking this as duplicate of bug 303199 - it is really a problem with virtualbox-ose-MODULES after all.

There are several workarounds: Use virtualbox from virtualbox.org (which has a Debian repository, too), install the modules manually (module-assistant, has been posted several times when this happened) or wait with the kernel upgrade until virtualbox-ose-modules has caught up (not recommended though!). For the last workaround, you can "just" boot the previous kernel from the Grub/bootloader menu (not recommened, since this kernel has known security issues).

Changed in virtualbox-ose:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.