Hey Everyone,
After updating I’m getting this new error related to virtualbox at launch. Wondering if there’s any way to make it stop appearing.
Thanks.
Apparently a fixed virtualbox module has been release, try updating and see if that fixes it.
Also it is worth thinking about migrating to use KVM so that you do not depend of 3rd party virtualbox.
Hey Barry,
I updated and got this an hour ago or so. I think it might be the most up to date one that’s causing this issue?
I also went ahead and uninstalled virtualbox with sudo dnf rm VirtualBox but the error in question still keeps appearing.
I’m sort of used to virtualbox being buggy with every update but this is a new one for me.
Thanks.
Confirmed - latest dnf update bumps the kernel but the modules for Vbox still fail to compile:
┌─🎩 lurcher cache/akmods/VirtualBox🔒
├─
└─➜ ls -al 13:50 Sat 14-Mar
Permissions Size User Date Modified Name
drwxr-xr-x@ - root 14 Mar 13:49 .
drwxr-xr-x@ - akmods 4 Feb 00:00 ..
.rw-r--r--@ 18k root 14 Mar 13:49 .last.log
.rw-r--r--@ 34k root 17 Feb 12:54 7.2.6-1-for-6.18.10-200.fc43.x86_64.log
.rw-r--r--@ 34k root 20 Feb 11:41 7.2.6-1-for-6.18.12-200.fc43.x86_64.log
.rw-r--r--@ 34k root 26 Feb 15:09 7.2.6-1-for-6.18.13-200.fc43.x86_64.log
.rw-r--r--@ 34k root 7 Mar 17:04 7.2.6-1-for-6.18.16-200.fc43.x86_64.log
.rw-r--r--@ 18k root 12 Mar 16:49 7.2.6-1-for-6.19.6-200.fc43.x86_64.failed.log
.rw-r--r--@ 18k root 14 Mar 13:49 7.2.6-1-for-6.19.7-200.fc43.x86_64.failed.log
Doesn’t bother me as I don’t use it, but it’s going to keep puking this error until version 7.2.6-1 is corrected and released.
There’s a fix here if you really want ti corrected ASAP.
Ah so this is a “known” issue then?
I can wait as long as my computer doesn’t brick. I mostly use this for browsing and games when I’m not working, so I can wait.
Thanks Steve.
The failed to build the virtualbox module only affects virtualbox, nothing else should be affected.
If you want to stop seeing the error then remove the akmods for virtualbox.
I might just wait on this one to update for now. in this case since it’s still working. I have another issues i’m troubleshooting when i have time this weekend. I forget the exact command to run to clean out the akmods in any case.
Thanks for your time. 
update the akmod-VirtualBox rpm from the testing repo:
$ dnf repoquery --repo=rpmfusion-free-updates akmod-VirtualBox
akmod-VirtualBox-0:7.2.6-1.fc43.x86_64
$ dnf rq --repo=rpmfusion-free-updates-testing akmod-VirtualBox
akmod-VirtualBox-0:7.2.6-2.fc43.x86_64
$ dnf changelog --repo=rpmfusion-free-updates-testing akmod-VirtualBox |head
Listing all changelogs
Changelogs for akmod-VirtualBox-7.2.6-2.fc43.x86_64
* Wed Feb 18 12:00:00 2026 Sérgio Basto <sergio@serjux.com> - 7.2.6-2
- Fixes for kernel 4.19
* Fri Jan 30 12:00:00 2026 Sérgio Basto <sergio@serjux.com> - 7.2.6-1
- Update to 7.2.6
there is a typo in the changelogs 4.19 => 6.19
update:
sudo dnf up --repo=rpmfusion-free-updates-testing akmod-VirtualBox
consider migrating to KVM, 
3 Likes
This is not being buggy, but inherent to every software requiring building kernel
modules: they have to stay compatible with the linux kernel.
Sorry I should’ve chosen my words a little better.
I meant that I’m used to vmware taking a while to update with new kernels and fedora versions.
Interesting. I am on Fedora 42 (Workstation/KDE/X11) x86_64 and I have not had any VirtualBox kmod issues with VirtualBox 7.2.6:
$ sudo cat /var/cache/akmods/VirtualBox/7.2.6*.log | grep -i "akmods: successful."
2026/02/18 00:31:38 akmods: Successful.
2026/02/21 20:23:00 akmods: Successful.
2026/02/26 11:11:41 akmods: Successful.
2026/02/10 11:44:40 akmods: Successful.
2026/02/18 00:35:08 akmods: Successful.
2026/03/11 16:24:09 akmods: Successful.
2026/03/11 16:25:16 akmods: Successful.
2026/03/12 11:29:49 akmods: Successful.
2026/03/14 22:31:35 akmods: Successful.
$ sudo ls -tr /var/cache/akmods/VirtualBox/*7.2.6*.rpm | sed 's/.*\///'
kmod-VirtualBox-6.18.8-100.fc42.x86_64-7.2.6-1.fc42.x86_64.rpm
kmod-VirtualBox-6.18.10-100.fc42.x86_64-7.2.6-1.fc42.x86_64.rpm
kmod-VirtualBox-6.18.9-100.fc42.x86_64-7.2.6-1.fc42.x86_64.rpm
kmod-VirtualBox-6.18.12-100.fc42.x86_64-7.2.6-1.fc42.x86_64.rpm
kmod-VirtualBox-6.18.13-100.fc42.x86_64-7.2.6-1.fc42.x86_64.rpm
kmod-VirtualBox-6.18.13-100.fc42.x86_64-7.2.6-2.fc42.x86_64.rpm
kmod-VirtualBox-6.18.16-100.fc42.x86_64-7.2.6-2.fc42.x86_64.rpm
kmod-VirtualBox-6.19.6-100.fc42.x86_64-7.2.6-2.fc42.x86_64.rpm
kmod-VirtualBox-6.19.7-100.fc42.x86_64-7.2.6-2.fc42.x86_64.rpm
That’s about a month of kernel updates (or manual rebuilding for whatever reason).
The 6.19.6 and 6.19.7 kernel updates for Fedora 42 went smoothly here. I am only a casual user of VirtualBox, but I would certainly notice kmod building issues/failures.
I bet because akmod-VirtualBox-7.2.6-2 that provides the needed fix landed earlier in
the rpmfusion-free-updates F42 repo than in F43. I don’t know why.
dnf --refresh list --showduplicates --enablerepo=*testing akmod-VirtualBox
[...]
Available packages
akmod-VirtualBox.x86_64 7.2.2-1.fc43 rpmfusion-free
akmod-VirtualBox.x86_64 7.2.6-1.fc43 rpmfusion-free-updates
akmod-VirtualBox.x86_64 7.2.6-2.fc43 rpmfusion-free-updates-testing
dnf --refresh list --showduplicates --enablerepo=*testing --releasever=42 akmod-VirtualBox
[...]
Available packages
akmod-VirtualBox.x86_64 7.1.6-1.fc42 rpmfusion-free
akmod-VirtualBox.x86_64 7.2.6-2.fc42 rpmfusion-free-updates
TZ=UTC date
Sun Mar 15 06:39:09 AM UTC 2026
In this case i’ll take a look this weekend.
Thanks, sorry my responses are so slow I usually only work on technical problems on my own system on the weekends.