Virtualbox in repo does not work with kernel 6.14

[rambo919]

OK so not the fault of whonix, after a kernel update it happened again, could not run any VM because the dkms driver was not availably.

The fix was to reinstall virtualbox-dkms, seems like the kernel updating did not pull through the dkms from this already installed package?

Did a restart now to make sure and running VM's still works.

Disabled test and a few actually useless third party repos today.... dunno if it updated from test instead of main and the problem lay there?

[Stevo]

I would suggest that trying to install it from Oracle really messed up your setup, since MX's virtualbox package depends on the matching virtualbox-dkms. Can't have it without the dkms. Note that it also brings in our guest-additions iso package.

Code: Select all

$ apt show virtualbox

Package: virtualbox
Version: 7.0.22-0.1~mx23+1
Priority: optional
Section: contrib/misc
Maintainer: Steven Pusser <stevep@mxlinux.org>
Original-Maintainer: Debian Virtualbox Team <team+debian-virtualbox@tracker.debian.org>
Installed-Size: 134 MB
Depends: adduser, iproute2, procps, virtualbox-dkms (>= 7.0.22-0.1~mx23+1) | virtualbox-source (>= 7.0.22-0.1~mx23+1) | virtualbox-modules, virtualbox-guest-additions-iso, virtualbox-qt (= 7.0.22-0.1~mx23+1), python3 (<< 3.12), python3 (>= 3.11~), python3.11, python3:any, libc6 (>= 2.34), libcurl3-gnutls (>= 7.16.2), libdevmapper1.02.1 (>= 2:1.02.97), libgcc-s1 (>= 3.0), libgl1, libgsoap-2.8.124 (>= 2.8.124), liblzf1 (>= 1.5), libpng16-16 (>= 1.6.2-1), libsdl2-2.0-0 (>= 2.0.12), libssl3 (>= 3.0.0), libstdc++6 (>= 12), libtpms0 (>= 0.8.0~dev1), libvncserver1 (>= 0.9.10), libvpx7 (>= 1.12.0), libx11-6, libxml2 (>= 2.7.4), libxt6, zlib1g (>= 1:1.1.4)
Recommends: libqt5core5a (>= 5.15.1), libqt5gui5 (>= 5.0.2) | libqt5gui5-gles (>= 5.0.2), libqt5opengl5 (>= 5.0.2), libqt5widgets5 (>= 5.0.2), libxcb1, libxcursor1 (>> 1.1.2), libxext6
Suggests: vde2
Conflicts: virtualbox-2.0, virtualbox-2.1, virtualbox-2.2, virtualbox-3.0, virtualbox-3.1, virtualbox-3.2, virtualbox-4.0, virtualbox-4.1, virtualbox-4.2, virtualbox-4.3, virtualbox-5.0, virtualbox-5.1, virtualbox-5.2, virtualbox-6.0, virtualbox-6.1, virtualbox-7.0

[Stevo]

You are also not really clear about whonix, since it also runs in a virtual machine, and may insist on its own version of virtualbox. So it's also still a really prime suspect.

You may have to set MX to install recommended packages by default if you want to use third-party repos.

[rambo919]

You are also not really clear about whonix, since it also runs in a virtual machine, and may insist on its own version of virtualbox. So it's also still a really prime suspect.

You may have to set MX to install recommended packages by default if you want to use third-party repos.

That was removed a while ago, not a factor anymore. It only installs packages when it's install script is explicitly run anyway.

But yeah unless someone else also gets this problem I guess it's a bit of a nothingburger.... I most likely will be doing a clean install when the next major MX comes out anyway.

The (kinda temp) fix at least is simple enough.... not nearly the level of problems VMWare has given me.