If the features in the VirtualBox extensions pack are just optional for your use, you can use VirtualBox still on Fedora Silverblue - but just with USB1 support and without the other features it provides.

If you really need the extensions, then I think you will have to use normal, non-Silverblue Fedora for now. The solution VirtualBoxĪs far as I’m aware, there isn’t a solution to use VirtualBox extensions on Silverblue. It’s also possible to compile software an install it locally or in /usr/local/.)īut the VirtualBox extension pack isn’t any of that. (Or you run it in containers with podman, toolbox, and Flatpak. (So, do not use it unless it’s for 100% personal use only or if you pay Oracle for it under their terms.) Back to the problemĪs Silverblue’s OS partition is basically read-only, you cannot add software on top of the base except as RPMs using rpm-overlay. They release the extensions as personal use only and go after people (with lawyers) who use it for anything other than personal use. The licensing? Oracle intentionally muddles with it. Yeah, a lot of what’s in the extension pack is actually useful and provided by default in other VMs (such as qemu and anything powered by libvirt). VirtualBox itself is Open Source, but the extension pack adds “ USB 2.0 and USB 3.0 devices, VirtualBox RDP, disk encryption, NVMe and PXE boot for Intel cards”. Explanation of the (intentional) license issues The reason why Oracle doesn’t include it in VirtualBox is due to licensing. The filename is Oracle_VM_VirtualBox_Extension_Pack-6.1.12.vbox-extpack, found from Downloads – Oracle VM VirtualBox However, VirtualBox’s extension pack (which is what is asking about) is not in an RPM, so you cannot overlay it on Silverblue. VirtualBox is in an RPM and can be installed with rpm-ostree.

I’m guessing probably knows some of this already (for the extensions pack case), but here’s some detailed background for everyone and some suggestions on what can do further down: Background info

Vbox extension pack install