Sweede
July 18, 2026, 4:38am
1
After upgrading to almalinux 9.8 from 9.7 Rpm fusion Virtual Box won’t run anymore, since Akmod fails to rebuild vboxdrv. Any help or do I need to revert to 9.7 to get my Virtual Box running again? Is this an rpm fusion issue with the Virtual Box package?
Hello,
This is most likely the same issue described below.
It’s highly probable that something was backported to the Alma 9.8 kernel,
causing a module that built successfully in 9.7 to fail to build in the current version.
As a workaround, use the 9.7 kernel.
I think your only option is to wait until a new version of VirtualBox is released.
オープン 03:42PM - 02 Jun 26 UTC
閉鎖 04:13PM - 02 Jun 26 UTC
bug
### Version
7.1.18
### Host OS Type
Linux
### Host OS name + version
AlmaLi… nux 9.8
### Host Architecture
x86
### Guest OS Type
all
### Guest Architecture
x86
### Guest OS name + version
_No response_
### Component
Host Installer
### What happened?
vboxconfig fails to build vboxdrv on AlmaLinux 9.8 kernel 5.14.0-687.5.3.el9_8.x86_64
Workaround is to reboot the updated system with AlmaLinux 9.7 kernel 5.14.0-611.55.1.el9_7.x86_64. vboxconfig command succeeds with that kernel, while the rest of the system stays updated to AlmaLinux 9.8 rpms.
Same error both on VirtualBox-7.1-7.1.18 and VirtualBox-7.2-7.2.8
### How can we reproduce this?
```
$ uname -r
5.14.0-687.5.3.el9_8.x86_64
$ sudo vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
$ tail -2 /var/log/vbox-setup.log
make[1]: *** [Makefile:1968: /tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile-footer.gmk:146: vboxdrv] Error 2
```
- maybe relevant errors from the vbox-setup.log:
```
/tmp/vbox.0/r0drv/linux/timer-r0drv-linux.c: In function ‘rtTimerLinuxStdCallback’:
/tmp/vbox.0/r0drv/linux/timer-r0drv-linux.c:754:37: error: implicit declaration of function ‘from_timer’; did you mean ‘mod_timer’? [-Werror=implicit-function-declaration]
754 | PRTTIMERLNXSUBTIMER pSubTimer = from_timer(pSubTimer, pLnxTimer, u.Std.LnxTimer);
| ^~~~~~~~~~
| mod_timer
/tmp/vbox.0/r0drv/linux/timer-r0drv-linux.c:754:70: error: ‘u’ undeclared (first use in this function); did you mean ‘up’?
754 | PRTTIMERLNXSUBTIMER pSubTimer = from_timer(pSubTimer, pLnxTimer, u.Std.LnxTimer);
| ^
| up
```
** workaround **
```
$ sudo grubby --set-default="/boot/vmlinuz-5.14.0-611.55.1.el9_7.x86_64"
$ sudo reboot
$ uname -r
5.14.0-611.55.1.el9_7.x86_64
$ sudo vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
$ tail -2 /var/log/vbox-setup.log
Building the net filter module.
Building the net adapter module.
```
[vbox-setup.log](https://github.com/user-attachments/files/28516827/vbox-setup.log)
### Did you upload *all* of your necessary log files, screenshots, etc.?
- [x] Yes, I've uploaded all pertinent files to this issue.
Thank you.