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

Fedora 19 – Schrödinger’s Cat – preview Now that the first beta edition of what will become Fedora 19 has been released, and almost all the accepted features are at 100% completion, I downlo...
How to install Markpado Markdown editor on Fedora 23 KDE This article shows how to install Markpado on Fedora 23 KDE. The steps should also work on any other distribution that's based on Fedora and uses the ...
Fedora 23 Cinnamon: Screenshots Fedora 23, the latest edition of the Fedora Linux distribution, was released earlier today. It is the first edition of Fedora that features a Cinna...
Have a Happy Holidays and give GRUB a look to match your mood Not too long ago, it was January, and in a few days, it will be another month of January. Time really does fly. But what can we do? Go with the...
The first thing to do after installing Linux Mint Debian 201204 Linux Mint Debian is a line of desktop distribution based on Debian, developed by the same group responsible for Linux Mint, a desktop distribution ba...
How to dual-boot Linux Mint 17 and Windows 8 on a PC with UEFI firmware This tutorial shows how to dual-boot Linux Mint 17 and Windows 8 on a PC with UEFI firmware. The computer used for the test installation is not an OEM...

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 *

*