Bug 612971 - the VirtualBox kernel modules are not updated if a new kernel is installed
Summary: the VirtualBox kernel modules are not updated if a new kernel is installed
Alias: None
Product: Fedora
Classification: Fedora
Component: dkms
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matt Domsch
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-09 12:40 UTC by Joachim Backes
Modified: 2010-09-13 07:00 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-09-13 06:59:20 UTC

Attachments (Terms of Use)

Description Joachim Backes 2010-07-09 12:40:24 UTC
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 06:59:20 UTC
My error: I forgot to install dkms

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