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

Install Cinnamon 1.4 on Fedora 17 The just released Fedora 17 offers a choice of four main desktop environments - GNOME 3, KDE, LXDE and Xfce. All have their loyal base, but there is a...
How to dual-boot Fedora 18 and Windows 8 on 1 HDD, with GRUB in a PBR This is the latest article on Fedora on this website. To view the complete list of Fedora-related articles, visit the distribution's category page at ...
How to upgrade Fedora 20 Cinnamon to Fedora 21 Cinnamon FedUp (FEDora UPgrader) is the recommended tool for upgrading a recent Fedora installation. It's a very neat tool for upgrading a system and I think o...
Using Apache SparkR to power Shiny Applications Editor: This is part 1 of a multi-part article published by SparkIQ Labs, a Big Data outfit based in Kampala, Uganda. The objective of this blog ...
Restore the Windows bootloader to MBR after dual-booting with Linux If you are reading this, you have likely attempted or actually set up a dual-boot system between your favorite Linux distribution and Windows. And if ...
Fedora 23 KDE screenshots Fedora 23 is the latest edition of the Fedora Linux distribution, released just this week. The first screenshots from a Fedora 23 test installation...

We Recommend These Vendors and Free Offers

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).

Want to become an expert ethical hacker and penetration tester? Request your free video training course of Online Penetration Testing and Ethical Hacking

Whether you're new to Linux or are a Linux guru, you can learn a lot more about the Linux kernel by requesting your free ebook of Linux Kernel In A Nutshell.


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 *

*