As the topic states virtualbox will not open vm’s using kernel 6.19.6. rebooting back to kernel 6.18 everything works as expected.I have virtualbox installed from rpmfusion.I have tried reinstalling virtualbox with no success.
VBox TestBuils. They works.
remove rpmfusion’s VB
download VB (with kernel 6.19.x compile fixes) from here:
Packages you need:
- Linux 64-bit
- Extension Pack
from Latest 7.2.x test builds
install VB-Testbuild with “sudo ~/Downloads/VirtualBox-*-Linux_amd64.run install”
adjust the path where you downloaded the package, usually ~/Downloads.
to remove VB-Testbuild use option “uninstall” , until VB and rpmfusion releases a newer VB version (7.2.7.x)
keep the package “*VirtualBox-*-Linux_amd64.run” until that date !
install the extension pack under VB
reboot to get the modules compiled (kernel-devel is installed ?)
Note:
some time ago when I uninstalled elder VB-Testbuilds I’ve seen that some/all desktop icons are gone too.
Fix: “sudo dnf reinstall shared-mime-info”
Thanks, saved my butt.
The problem is described here:
Your workaround worked for me 
$ inxi -S
System:
Kernel: 6.19.6-200.fc43.x86_64 arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.6.2 Distro: Fedora Linux 43 (KDE Plasma Desktop
Edition)
1 Like
I’m having the same problem. No workaround listed, the last post on that link says there is no solution at this time. How can I get virtualbox 7.2.6 to run on 6.19.6?
Thank you for the reply’s I used to use the test builds from Oracle but switched to rpmfusion several years ago.i may give it some time and see if the issue is solved as i do not use virtualbox except to check out newer systems.If it does not get resolved soon I may switch back to the test builds.I would like to add I updated today and got 6.19.7 and it has the same issue.
I need it to run my business so I’m in a bit of a bind. I installed with the RPM Fusion method.
Tried this but just got an error:
sudo akmods --force
And the build log typing sudo cat /var/cache/akmods/VirtualBox/7.2.6-1-for-6.19.6-200.fc43.x86_64.failed.log gives this error:
ERROR: modpost: module vboxdrv uses symbol cr4_update_irqsoff from namespace module:kvm,kvm-amd,kvm-intel, but does not import it.
ERROR: modpost: module vboxdrv uses symbol cr4_read_shadow from namespace module:kvm,kvm-amd,kvm-intel, but does not import it.
ERROR: modpost: module vboxdrv uses symbol __flush_tlb_all from namespace module:kvm,kvm-amd,kvm-intel, but does not import it.
Here’s what may get you back up and running again:
I uninstalled the existing VirtualBox installation using `sudo dnf remove VirtualBox\*`, downloaded the test build from the linked page (above), make sure to choose the latest 7.2.x test build (there’s also 7.1.x available). As @sixpack13 mentioned above, this is an installer file that you need to run.
Make it executable:
chmod +x VirtualBox-7.2.7-173119-Linux_amd64.run
(Your file name may be different because there is a build number in it that is subject to change.)
Then do something like:
sudo ./VirtualBox-7.2.7-173119-Linux_amd64.run install
This will re-install VirtualBox.
Open VirtualBox from the application menu and invoke the File menu, then Tools, then Extensions and locate the Extension Pack file that you probably downloaded sometime earlier (since you have used VirtualBox previously).
This worked fine for me, I am currently using my virtual machine without problems right now.
Note: Running a program that you downloaded from the internet with administrator rights (`sudo`) will allow that program to do anything with your system, so please do this at your own risk. I’ve done it because I trust the virtualbox.org website.
If you can stay on kernel 6.18 until it is solved as virtualbox works as it should .
1 Like
That’s a great idea thank you. Will it automatically show up when fixed in my updates?
It should show an update from rpmfusion.I have not used it but I am pretty sure there is an rpmfusion forum.
you should follow the link @vgaetera provided.
there the first entry.
click that.
scroll down to the last entry (it’s a duplicate)
click that too
find the comments from @klaus-vb
read that the workaround is the testbuild
that’s a bad idea.
kernel 6.19.x wasn’t created just for fun.
and in time fedora will usually remove kernel 6.18.x from your box (your special care is needed it won’t)
even since new kernel 6.19.x releases hitting the scene each 7-10 days
to sum up: your good idea only keeps good for ~3 weeks
Updated akmods resolves issue for me.
akmods-0.6.2-9.fc43.noarch
It’s quite easy to use older kernels and keep Fedora from updating them. Just put:
exclude=kernel*
into /etc/dnf/dnf.conf, and you’re done.
That said, it’s a mystery to me why anyone would use Fedora for mission-critical applications. Fedora is bleeding edge, by design, and things WILL break.
1 Like
rpmfusion provides now a fix of akmod-VirtualBox in the rpmfusion-free-updates-testing
repo. Run thus:
dnf -y --refresh --enablerepo=rpmfusion-free-updates-testing update akmod-VirtualBox
then wait for akmods to build the kernel modules.
It compiles for the 6.19.6-200.fc43.x86_64 kernel. I haven’t tested VirtualBox.
I haven’t tested also with the 6.19.7-200.fc43.x86_64 kernel
Tested now: it compiles.
Also, dnf will never remove the currently running kernel.
If the running kernel is the oldest one on the system and dnf is doing a kernel update, then it removes the second-oldest kernel to make way for the new one.
Works for me, too, but I had to fumble a bit to get it to install. Here’s my path to success:
# This is all done as sudo.
# 1. Remove the unstable build (if installed).
./VirtualBox-7.2.7-173119-Linux_amd64.run uninstall
# 2. Install VirtualBox from the normal (non-testing) rpm-fusion repository; it did not work when I initially did step 3 before step 2.
dnf install VirtualBox akmod-VirtualBox
# 3. Enable rpmfusion-free-updates-testing and install akmod-Virtualbox from there.
dnf -y --refresh --enablerepo=rpmfusion-free-updates-testing update akmod-VirtualBox
# 4. Restart the vboxdrv systemd service (or maybe restart the computer).
systemctl restart vboxdrv.service
Thanks @francismontagnac !
1 Like
Date sent: Sat, 14 Mar 2026 09:00:52 +0000
Send reply to: Fedora Discussion incoming+437804d63cd1ed244675ec96a9c17d48@fedoraproject.discoursemail.com
workstation kernel
Daniel Kraus bovender March 14
Works for me, too, but I had to fumble a bit to get it to install. Here’s my
path to success:This is all done as sudo.
1. Remove the unstable build (if installed).
./VirtualBox-7.2.7-173119-Linux_amd64.run uninstall
2. Install VirtualBox from the normal (non-testing) rpm-fusion repository; it
did not work when I initially did step 3 before step 2.
dnf install VirtualBox akmod-VirtualBox3. Enable rpmfusion-free-updates-testing and install akmod-Virtualbox from
there.
dnf -y --refresh --enablerepo=rpmfusion-free-updates-testing update
akmod-VirtualBox4. Restart the vboxdrv systemd service (or maybe restart the computer).
systemctl restart vboxdrv.service
Thanks @francismontagnac !
Had it working on my notebook, but then tried to install on my
other 6 machines, and they all failed to build the akmods?
Ended up having the install from the testing repo, and then they
worked.
rpm -qa | grep -i “virtualbox|akmod”
VirtualBox-kmodsrc-7.2.6-1.fc43.noarch
VirtualBox-server-7.2.6-1.fc43.x86_64
VirtualBox-vnc-7.2.6-1.fc43.x86_64
VirtualBox-webservice-7.2.6-1.fc43.x86_64
VirtualBox-devel-7.2.6-1.fc43.x86_64
virtualbox-guest-additions-7.2.6-1.fc43.x86_64
akmods-0.6.2-9.fc43.noarch
VirtualBox-7.2.6-1.fc43.x86_64
akmod-VirtualBox-7.2.6-2.fc43.x86_64
kmod-VirtualBox-7.2.6-2.fc43.x86_64
kmod-VirtualBox-6.18.16-200.fc43.x86_64-7.2.6-2.fc43.x86_64
kmod-VirtualBox-6.19.6-200.fc43.x86_64-7.2.6-2.fc43.x86_64
kmod-VirtualBox-6.19.7-200.fc43.x86_64-7.2.6-2.fc43.x86_64
akmods
Checking kmods exist for 6.19.7-200.fc43.x86_64 [ OK ]
So, have it working on all 7 of my Fedora 43 machines
1 Like