Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 612971 - the VirtualBox kernel modules are not updated if a new kernel is installed
the VirtualBox kernel modules are not updated if a new kernel is installed
Product: Fedora
Classification: Fedora
Component: dkms (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Matt Domsch
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-09 08:40 EDT by Joachim Backes
Modified: 2010-09-13 03:00 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-09-13 02:59:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joachim Backes 2010-07-09 08:40:24 EDT
Description of problem:
I'm running F13 and VirtualBox from virtualbox.org (not Virtualbox-ose). Each time a new kernel is installed, the virtualbox box driver modules are *not
rebuilt*. So, after rebooting my box and starting VirtualBox for the first time (after kernel update), the VirtualBox start is
rejected and a PopupUp appears saying something as "Fedora users should
install DKMS", and I have to do "/etc/init.d/vboxdrv setup" manually.

After having done "/etc/init.d/vboxdrv setup" once, then VirtualBox starts flawless (until the next kernel update).

But in my box, the most recent (??) version of dkms is installed:

Version-Release number of selected component (if applicable):

How reproducible:
Each time after the kernel is updated

Steps to Reproduce:
1.Update kernel
3.Start VirtualBox
Actual results:
VirtualBox rejects start

Expected results:
The VM is booted

Additional info:
Comment 1 Joachim Backes 2010-09-13 02:59:20 EDT
My error: I forgot to install dkms

Note You need to log in before you can comment on or make changes to this bug.