Fedora, Tutorials/Tips

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

Related Post:  Understanding the Technology Behind Most Online Casinos and Slot Games

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 Post:  Solution to freezing SSH sessions on Ubuntu 16.10

Subscribe to LinuxBSDos.com

Subscribe to receive the latest articles in your Inbox

Trust me, you'll not be spammed...

Please share:
Tags:

We Recommend These Vendors and Free Offers

Google has got competition, because Presearch is building a blockchain-based search engine controlled by the community. At $0.15 a token, you can participation in Lot 3 of the token sale by clicking here

Open Money is building a solution that will run mainstream software on blockchain tech. Click here to get free tokens that will be the digital currency of the platform

COMSA allows centralized businesses to adopt blockchain technology. The token sale starts soon! Sign up for free by clicking here

Register now for Blockchain & Cryptocurrency Con 2018, international conference on blockchain technnology in Dallas, TX (USA), Feb. 23-24, 2018. Students can register at a 50% discount.

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


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 *

*