Bug 612971

Summary:	the VirtualBox kernel modules are not updated if a new kernel is installed
Product:	[Fedora] Fedora	Reporter:	Joachim Backes <joachim.backes>
Component:	dkms	Assignee:	Matt Domsch <matt_domsch>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	13	CC:	matt_domsch, tcallawa
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-13 06:59:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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:
dkms-2.1.0.1-1.fc12.noarch.


Version-Release number of selected component (if applicable):
dkms-2.1.0.1-1.fc12.noarch.

How reproducible:
Each time after the kernel is updated

Steps to Reproduce:
1.Update kernel
2.Reboot
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