Precise virtualbox packages do not work with -trusty hardware enablement stack

Bug #1349407 reported by David Partain
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Greetings,

If you install a vanilla precise Ubuntu machine and upgrade to the latest Hardware Enablement Stack kernel doing:

sudo apt-get install linux-generic-lts-trusty libgl1-mesa-glx-lts-trusty xserver-xorg-lts-trusty linux-image-generic-lts-trusty

(or similar) and reboot, your precise machine will then have a 3.13 kernel. That's Goodness.

However, if you then try to install the "standard" (from universe) virtualbox packages from the standard repository, it'll fail. The current version of virtualbox-guest-dkms in precise (4.1.12) does not work with the new 3.13 kernel and virtualbox will not work.

Just do:

sudo apt-get install virtualbox

and you'll get:

Building initial module for 3.13.0-32-generic
Error! Bad return status for module build on kernel: 3.13.0-32-generic (x86_64)
Consult /var/lib/dkms/virtualbox/4.1.12/build/make.log for more information.
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules * No suitable module for running kernel found
[fail]
invoke-rc.d: initscript virtualbox, action "restart" failed.

and if you look in /var/lib/dkms/virtualbox/4.1.12/build/make.log you'll see that it simply doesn't build. I can provide such a log, if that'd be helpful.

You can work around this by installing directly from virtualbox.org, but it'd be very very very nice if the 'precise' packages in universe were updated to work with 3.13.

Cheers,

David

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
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.