Is there any guide on setting up VirtualBox on Silverblue?

Hi!

I’m trying to run a Windows11 VM in Fedora Silverblue. It seems to not be straightforward but doable, as mentionned here and here, but I can’t get it to work. Installing the rpm from VIrtualBox’s website doesn’t work, it requires setting up the kernel module with vboxconfig but fails because of the read-only root:

rm: cannot remove '/sbin/rcvboxdrv': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxdrv': File exists
./routines.sh: line 155: /lib/systemd/system/vboxdrv.service: Read-only file system
rm: cannot remove '/sbin/rcvboxballoonctrl-service': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxballoonctrl-service': File exists
./routines.sh: line 155: /lib/systemd/system/vboxballoonctrl-service.service: Read-only file system
rm: cannot remove '/sbin/rcvboxautostart-service': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxautostart-service': File exists
./routines.sh: line 155: /lib/systemd/system/vboxautostart-service.service: Read-only file system
rm: cannot remove '/sbin/rcvboxweb-service': Read-only file system
ln: failed to create symbolic link '/sbin/rcvboxweb-service': File exists
./routines.sh: line 155: /lib/systemd/system/vboxweb-service.service: Read-only file system
ln: failed to create symbolic link '/etc/rc.d/rc0.d/K80vboxdrv': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc1.d/K80vboxdrv': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc2.d/K80vboxdrv': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc3.d/S20vboxdrv': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc4.d/S20vboxdrv': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc5.d/S20vboxdrv': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc6.d/K80vboxdrv': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc0.d/K65vboxballoonctrl-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc1.d/K65vboxballoonctrl-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc2.d/K65vboxballoonctrl-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc3.d/S35vboxballoonctrl-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc4.d/S35vboxballoonctrl-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc5.d/S35vboxballoonctrl-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc6.d/K65vboxballoonctrl-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc0.d/K65vboxautostart-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc1.d/K65vboxautostart-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc2.d/K65vboxautostart-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc3.d/S35vboxautostart-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc4.d/S35vboxautostart-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc5.d/S35vboxautostart-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc6.d/K65vboxautostart-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc0.d/K65vboxweb-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc1.d/K65vboxweb-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc2.d/K65vboxweb-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc3.d/S35vboxweb-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc4.d/S35vboxweb-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc5.d/S35vboxweb-service': No such file or directory
ln: failed to create symbolic link '/etc/rc.d/rc6.d/K65vboxweb-service': No such file or directory
ln: failed to create symbolic link '/sbin/vboxconfig': Read-only file system
vboxdrv.sh: Stopping VirtualBox services.
rm: cannot remove '/lib/modules/5.19.6-200.fc36.x86_64/misc/vboxdrv.ko': Read-only file system
rm: cannot remove '/lib/modules/5.19.6-200.fc36.x86_64/misc/vboxnetadp.ko': Read-only file system
rm: cannot remove '/lib/modules/5.19.6-200.fc36.x86_64/misc/vboxnetflt.ko': Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.dep.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.dep.bin.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.alias.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.alias.bin.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.softdep.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.symbols.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.symbols.bin.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.builtin.bin.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.builtin.alias.bin.10940.841025.1662535352, 301, 644): Read-only file system
depmod: ERROR: openat(/lib/modules/5.19.6-200.fc36.x86_64, modules.devname.10940.841025.1662535352, 301, 644): Read-only file system
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: You must sign these kernel modules before using VirtualBox:
  vboxdrv vboxnetflt vboxnetadp
See the documentation for your Linux distribution..
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

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.

The VirtualBox rpm from rpm-fusion also failed, telling me to run akmods which could not install the rpms it created because neither yum or dnf were available.

Has anyone gotten it to run on SIlverblue?

Thanks!