Regarding Fedora 19 kernel upgrades and VirtualBox kernel modules

My main desktop computer is powered by Fedora 19 on which I run at least a dozen guest operating systems using VirtualBox.

VirtualBox is my favorite software virtualization application. It’s really nice and easy to use. Installation packages are available for the major operating systems and distributions.

My setup works fine until I upgrade Fedora to a new kernel. On rebooting, any attempt to start a Guest OS fails with the error message shown in this image. Kernel driver not installed (rc=-1908).
Fedora 19 virtualbox vboxdrv error

Running the suggested systemctl command returns the output shown in this image.
VirtualBox kernel module error Fedora 19

And running the suggested command from that output returns the message shown in this image. I know for sure that DKMS is installed because rpm -q dkms returns dkms-2.2.0.3-17.fc19.noarch.
VirtualBox kernel module error Fedora 19

I have a pretty good idea what’s going on, but I needed conformation. Running vboxmanage gave me the info I was looking for.
VirtualBox kernel module error Fedora 19

So the system is running kernel 3.11.7, but a matching VirtualBox kernel module was not yet available. While I await the release of a matching kernel module, what’s the solution the problem with staring a Guest OS? Reboot and run the system using the older kernel. Within about four days, a matching VirtualBox kernel module was released and I’m now running it. Problem solved. So now I know to not panic whenever I upgrade the kernel in Fedora and Virtualbox fails to run any guest OS.
VirtualBox kernel module error Fedora 19

Related Posts

PC-BSD’s graphical firewall manager PC-BSD is a desktop-oriented, FreeBSD-based distribution with KDE as the default desktop environment. The version due to be released shortly is PC-BSD...
Guest account and user management on Mandriva 2011 Creating and managing user accounts are very basic tasks that you would need to perform on any operating system. If you are new to Linux and to Mandri...
Dual-booting PC-BSD 8.2 and Windows 7 In continuation of a series of articles on dual-booting Linux and BSD desktop distributions with Windows 7, this article presents a step by step guide...
How to install Moovida media center on Linux Mint 8 Moovida is a free media center application available for users of Linux and BSD desktop operating systems. It is developed by Fluendo S.A., an outfit ...
Qt Widgets and the Third Dimension Some people have been asking how to embed Qt painted content (and especially Qt widgets) in a 3d scene. As I’ve been wanting to do this ever since we ...
How to enable auto-login and create a guest user account on Fedora 14 Fedora is one of very few distributions that does not have the auto-login feature in its graphical user management tool. Auto-login allows the system ...

We Recommend These Vendors

Launch an SSD VPS in Europe, USA, Asia & Australia on Vultr's KVM-based Cloud platform starting at $5:00/month (15 GB SSD, 768 MB of RAM).

Deploy an SSD Cloud server in 55 seconds on DigitalOcean. Built for developers and starting at $5:00/month (20 GB SSD, 512 MB of RAM).


One Comment

  1. Andreas WERNER

    There is a kmod-VirtualBox.x86_64 : Metapackage which tracks in VirtualBox kernel module for newest kernel

    yum search kmod-VirtualBox

    Same problem for me with kmod-catalyst.x86_64

    I have installed AMD’s proprietary driver for ATI graphic cards out of rpmfusion. As long as there is no updated kmod-catalyst from rpmfusion I risk a black screen after a kernel update.

Leave a Comment

Your email address will not be published. Required fields are marked *

*