Latest update broke virtualbox

karypid

I just updated and got (among other updates) these:

Operation #311: upgrade
Date: 2021-10-25 10:36

    * virtualbox-common is upgraded from 6.1.26-214-1-x86_64 to 6.1.28-216-1-x86_64 with delta.
    * virtualbox-current is upgraded from 6.1.26-214-1-x86_64 to 6.1.28-216-1-x86_64.
    * linux-current is upgraded from 5.14.12-201-1-x86_64 to 5.14.14-202-1-x86_64 with delta.
...
    * linux-headers is upgraded from 5.14.10-83-1-x86_64 to 5.14.14-84-1-x86_64 with delta.
...
...

Now when I try to start any VM it comes back complaining that "The VirtualBox kernel modules do not match this version of VirtualBox". This is my running kernel and the list of installed linux packages:

karypid@ironyman ~ $ uname -a
Linux ironyman 5.14.12-201.current #1 SMP PREEMPT Sat Oct 16 14:33:39 UTC 2021 x86_64 GNU/Linux
karypid@ironyman ~ $ eopkg li | egrep "linux|virtualbox"
libressl-shim                               - Security override library for linux-steam-integration
libselinux                                  - SELinux runtime library
linux-current                               - Linux kernel image and modules (current)
linux-driver-management                     - Linux Driver Management
linux-driver-management-lightdm-integration - LDM Integration for LightDM
linux-firmware                              - Firmware required for many devices
linux-headers                               - Kernel's libc headers
linux-steam-integration                     - Helper for enabling better Steam integration on Linux
util-linux                                  - util-linux (Essential Linux utilties)
util-linux-32bit                            - 32-bit libraries for util-linux
util-linux-devel                            - Development files for util-linux
virtualbox-common                           - Common components for VirtualBox host packages
virtualbox-current                          - VirtualBox host modules for the linux-current kernel

As you can see I am using the "current" flavor of kernel/vbox.

I suppose the update is broken? Is there anything I can do to work around this currently? Can I compile the VBOX modules myself and how doe I go about doing that cleanly? I suppose I need to remove "virtualbox-current" so that I don't have the modules distributed by solus, but how do I compile the host modules myself?

algent

karypid karypid@ironyman ~ $ uname -a
Linux ironyman 5.14.12-201.current #1 SMP PREEMPT Sat Oct 16 14:33:39 UTC 2021 x86_64 GNU/Linux

You should use the new kernel: linux-current 5.14.14-202. Probably only a reboot it is needed since you updated your system.

karypid

Some more info:

karypid@ironyman ~ $ eopkg info -f virtualbox-current
/lib/modules/5.14.14-202.current/extra/vboxdrv.ko, type: data, size: 748360, sha1sum: f38512fa1218fc316cbe08fe7301d9c827e401cc
/lib/modules/5.14.14-202.current/extra/vboxnetadp.ko, type: data, size: 19384, sha1sum: 77ff18b020d2d5dfd6ce06db6738ca56a81fd056
/lib/modules/5.14.14-202.current/extra/vboxnetflt.ko, type: data, size: 60456, sha1sum: bbfb71ed1a4556866a31a77430456641bdf2d240
Package found in Solus repository:
Name                : virtualbox-current, version: 6.1.28, release: 216
Summary             : VirtualBox host modules for the linux-current kernel
Description         : VirtualBox is a free powerful open source solution for running other x86 and x86_64 operating systems
                      virtually on your computer.
                    
Installation Guide  : https://getsol.us/articles/software/virtualbox/en/
Licenses            : GPL-2.0-only
Component           : virt
Dependencies        : linux-current virtualbox-common 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 808.00 KB, Package Size: 154.00 KB
Reverse Dependencies: 

virtualbox-current package is not found in source repositories
karypid@ironyman ~ $ lsmod | grep vbox
vboxnetadp             28672  0
vboxnetflt             32768  0
vboxdrv               495616  2 vboxnetadp,vboxnetflt

Is there a way to revert back to the older version of the kernel/virtualbox? This has disrupted my workflow unfortunately. I'm looking for a quick workaround here...

I'll try installing the LTS packages now, hopefully those will work?

karypid

algent So I did reboot, twice. I don't know why, I kept getting that same error.

It now works and I suspect it may have to do with the update partially failing due to /boot space (see below)?

After installing the LTS kernel I had to run sudo clr-boot-manager update to pick up the LTS entry. That ran into disk space issues in /boot and I ended up deleting some old kernels and re-running. Once it completed successfully I rebooted and chose the non-LTS entry just for one last try (I had now manually run the boot manager updater and saw it succeed, so wanted to try again). It worked this time around and I ended up removing/deleting the LTS kernel I had just installed.

So my theory now is that during update something was not done properly in /boot and I ended up with this issue?

I've been using Solus for just over a year so I guess one needs to manually clean up old kernels every once in a while from /boot? Is there a command to do that?

algent

karypid I usually run sudo usysconf run -f and that deletes old kernels for me.