VirtualBox 7.1.8 does not work with 6.15 kernel

English Virtualization
1

Just a Heads-Up, the current VBox 7.1.8 from oss repo does not work with the new 6.15 kernel in the current TW 20250602 snapshot.
Upstream version 7.1.10 should work (but I have not tested).
Please see VBox 7.1.10 released

3 Likes
2

Thanks for the info. I built Kernel 6.15 myself to learn how to do it. It worked well but I did notice that VB wasn’t working.

I didn’t spend too much time on it so I had no clue why. Then I figured out how to remove my 6.15 so I could install the official 6.15 with no problems.

I hadn’t tried it on the official Tumbleweed Kernel 6.15 yet. I can always boot to the last 6.14 if I need it that bad.

3

I have the same problem!

4

Well, I guess that explains my earlier report I made today here…

Pretty much what I expected.

How do you get the upstream one to install? I tried that but ithe install complained about a missing library.

And now I just tried the “run installer” script - and that doesn’t work, either. First I get this which “claims” that it’s installed successfully:

sudo ./VirtualBox-7.1.8-168469-Linux_amd64.sh
[sudo] password for root:
Verifying archive integrity… 100% MD5 checksums are OK. All good.
Uncompressing VirtualBox for Linux installation 100%
VirtualBox Version 7.1.8 r168469 (2025-04-11T15:18:54Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python3.11, installing bindings…
Python found: python3, installing bindings…
Python 3.13 does not have package ‘distutils’, checking for ‘setuptools’…
Python 3.13 also does not have package ‘setuptools’. Skipping installation.
egrep: warning: egrep is obsolescent; using grep -E
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.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
User_FAQ – Oracle VirtualBox

We hope that you enjoy using VirtualBox.

The installation log file is at /var/log/vbox-install.log.

I looked at the log and it’s another massive pile of garbage with a ton of things like:

In file included from linux/SUPDrv-linux.c:42:
linux/…/SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file or directory

Then when I try to run it, I get this:

VirtualBox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (6.15.0-1-default) or it failed to
load. Please recompile the kernel module and install it by

       sudo /sbin/vboxconfig

     You will not be able to start VMs until this problem is fixed.

/opt/VirtualBox/VirtualBox: error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file: No such file or directory

And then when I try the “sudo /sbin/vboxconfig”, I get this:

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
egrep: warning: egrep is obsolescent; using grep -E
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.

I’m not running secure boot, so that’s not it.

So I guess we’re screwed until someone fixes this.

I earlier submitted a bug report to the openSUSE Bugzilla, so hopefully someone will look at this and we’ll have a fix. It’s a pretty significant issue for anyone using VirtualBox, so I expect they’ll pay attention to it soon enough.

5

And the latest VirtualBox 7.1.10 will not install either: requires libvpx version 7 and Tumbleweed is on version 9.

6

For the time being, ensure that a 6.14 kernel remains on your system, for instance by editing /etc/zypp/zypp.conf and adding a line that reads something like:

multiversion.kernels = latest,latest-1,running,6.14.6-2.1
1 Like
7

The fixed VB version arrived in factory and should be available with the next snapshot.

2 Likes