Virtualbox installation fails in 12.04.5 after upgrade from 3.11.0-26 to 3.13.0-39. "No suitable module for running kernel found"

Bug #1394113 reported by Lars Aberg
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Can not install Virtualbox * No suitable module for running kernel found [fail]
-------------------------------------------------------------
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.5 LTS"

3.13.0-39-generic #66~precise1-Ubuntu SMP Wed Oct 29 09:56:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

virtualbox 4.1.12-dfsg-2ubuntu0.6 Note! This version works with the older kernel.
-------------------------------------------------------------

Virtualbox installation fails in Ubuntu 12.04.5 LTS adm 64 after an upgrade
from kernel 3.11.0-26-generic #45~precise1-Ubuntu SMP Tue Jul 15 04:02:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
to kernel 3.13.0-39-generic #66~precise1-Ubuntu SMP Wed Oct 29 09:56:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Could not start virtualbox after the upgrade.
Removed virtualbox (apt-get purge virtualbox, did a reboot)
Installed virtualbox again
* No suitable module for running kernel found [fail]

sudo apt-get install virtualbox
---
  Setting up virtualbox (4.1.12-dfsg-2ubuntu0.6) ...
  * Stopping VirtualBox kernel modules [ OK ]
  * Starting VirtualBox kernel modules * No suitable module for running kernel found [fail]
 i nvoke-rc.d: initscript virtualbox, action "restart" failed.
  Processing triggers for python-central ...
  Setting up virtualbox-dkms (4.1.12-dfsg-2ubuntu0.6) ...
  Loading new virtualbox-4.1.12 DKMS files...
  First Installation: checking all kernels...
  Building only for 3.13.0-39-generic
  Building initial module for 3.13.0-39-generic
  Error! Bad return status for module build on kernel: 3.13.0-39-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]
------

      Since the installation fails the next message when starting virtualbox is obvious virtualbox
      WARNING: The character device /dev/vboxdrv does not exist.

History:
Did a fresh installation of Ubuntu 12.04.5 (on four computers) and did "Install updates" from Software manager.
Then did a successfull installation of Virtualbox and used it.
Next day did a update again from "Update Manager" including doing an update "New hardware support is available"
   (did this on two of the four computers used)

 - The update was done from "Update Manager" -> "New hardware support is available"
- Virtualbox does not work, dkms fails and a re-installation of virtualbox fails.
- This is repeatable. Have the same situation on four identical computers.

 3.11.0-26 to 3.13.0-39. "No suitable module for running kernel found"

Workaround now is to use virtualbox downloaded from Oracle on two upgraded computers (3.13.0-39) while using from repository on the two non upgraded computers that still runs 3.11.0-26

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: virtualbox 4.1.12-dfsg-2ubuntu0.6
ProcVersionSignature: Ubuntu 3.13.0-39.66~precise1-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Wed Nov 19 09:46:53 2014
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204)
MarkForUpload: True
SourcePackage: virtualbox
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBox.ModInfo:

Revision history for this message
Lars Aberg (lars-aberg) wrote :
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
Revision history for this message
Rus Newtron (techabsorbed) wrote :

Same deal for me. VirtualBox stopped working after upgrade and re-installation fails as described.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

this should be fixed with latest updates.

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