Failure to install on Centos9/10 Error building driver

[VersedBook0]

Attempting to install or update Virtualbox on Centos9 and after upgrade Centos10
the install fails during the setup script building the kernal module.
the appropriate lines from vbox_setup.log are:

Code: Select all

In file included from /tmp/vbox.0/combined-os-specific.c:64:
/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’? [-Wimplicit-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
/tmp/vbox.0/r0drv/linux/timer-r0drv-linux.c:754:70: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [scripts/Makefile.build:229: /tmp/vbox.0/combined-os-specific.o] Error 1
make[2]: *** Waiting for unfinished jobs....
# cmd_gen_symversions_c /tmp/vbox.0/linux/SUPDrv-linux.o

I've (re)installed kernel-devel and headers with no change

Can anyone point me to a solution?

[VersedBook0]

I should note that this started after a recent update of Centos a week or 2 ago. Up until then all worked ok.

[Liwiusz]

Just change boot option to previous kernel. This is common behavior of Virtualbox on CentOS. Sometimes kernel version is too new and VirtualBox did not catch up.

[VersedBook0]

I've fixed this by migrating to AlmaLinux.
The migration was fairly painless and everything now works.
I didn't want just a temporary solution that would possibly break again.

[Boxy]

I've fixed this by migrating to AlmaLinux.

Hmm...Once you start down the dark path, forever will it dominate your destiny, consume you it will.
As kernel patch 5.14.0-687 landet in RHEL 9 these days, I got the same problem and found a (questionable) solution that worked for me until we got an official solution.

[KloCZ2]

I can confirm that not just the latest 7.2 development version (as somebody already confirmed), but also latest 7.1 development version (VirtualBox-7.1-7.1.19_174041_el9-1.x86_64.rpm) fixed this situation on Linux (RHEL9) hosts.

But I also observed, that today have been erased 7.1 builds from Testbuild page (https://www.virtualbox.org/wiki/Testbuilds). Why is that? I believe that 7.1 version is still heavily used (as there are still some troubles with newer 7.2 version), probably is still actively developed (fortunately I was able to grab latest 7.1 version from Testbuilds page yesterday), so I believe that this production version deserves at least one stable version (7.1.20) to make public.

Is still possible to download these development versions somewhere ? I tried to access https://www.virtualbox.org/download/testcase/, but it gave me "You don't have permission to access this resource".

[KloCZ2]

I can confirm that not just the latest 7.2 development version (as somebody already confirmed), but also latest 7.1 development version (VirtualBox-7.1-7.1.19_174041_el9-1.x86_64.rpm) fixed this situation on Linux (RHEL9) hosts.

But I also observed, that today have been erased 7.1 builds from Testbuild page (https://www.virtualbox.org/wiki/Testbuilds). Why is that? I believe that 7.1 version is still heavily used (as there are still some troubles with newer 7.2 version), probably is still actively developed (fortunately I was able to grab latest 7.1 version from Testbuilds page yesterday), so I believe that this production version deserves at least one stable version (7.1.20) to make public.

Is still possible to download these development versions somewhere ? I tried to access https://www.virtualbox.org/download/testcase/, but it gave me "You don't have permission to access this resource".

Hmm, as I see, yesterday was published (only) version 7.2.10 (which is probably very broken, as several users reported), and no 7.1.X (I suppose 7.1.20) version. Sad situation. Could you please re-enable 7.1 links on Testbuild pages and/or publish testing version 7.1.19_174041 (or newer, if there's newer) as 7.1.20 stable version? Or could you please explain, why the 7.1 branch is not supported anymore and why 7.1 testing versions were hidden/erased ? I assume that there are still lot of users, those have a good reason to keep 7.1.X branch on their systems for some time yet. Thanks!

[multiOS]

See https://www.virtualbox.org/wiki/Download_Old_Builds - Official support for 7.1 ended in March 2026. with its final 7.1.18 maintenance release.

[KloCZ2]

See https://www.virtualbox.org/wiki/Download_Old_Builds - Official support for 7.1 ended in March 2026. with its final 7.1.18 maintenance release.

Ok, thanks for the info. I still don't understand too much, why the 7.1 test version (build 174041 is probably the last one) cannot be published - as devel version or "last stable version" for 7.1 brach (as 7.1.20). There were troubles with previous versions (7.1.18 and 7.2.8) at least on RHEL systems (rebase of 9.8 and 10.2 versions), and that newer build 174041 is working in this case, it looks like. So I believe that users and also 7.1 branch deserve this "finalization".