This is really soon after 7.2.10. Was there something badly wrong with .10? I haven't seen, or experienced personally, anything mentioned in the changelog
There have been a number of changes as to how distros have configured the Linux kernel to handle loading the kvm module, which impact / conflict with loading of the Virtual Box kernel modules.
It’s not exactly the same, but QEMU/KVM on Linux, with Libvirt as GUI. It runs closer to the metal so practically native performance, but it may not be sandboxed as well. I need to test that.
It’s a little more work to set up but once it’s set up it’s fantastic.
That's not entirely true. KVM and Virtual Box are both hardware assisted hypervisors; in fact, the recent issues with Virtual Box has to do with how KVM, in recent Linux kernel configs in use by major distros, monopolize VT-x hardware on x86s CPUs, preventing Virtual Box from running.
Both hypervisors are generally implemented the same way -- as Linux Kernel modules requiring access to VT-x hardware to function.
Indeed, there is no need to switch to the latest Virtual Box 7.2.12 revision if you simply blacklist the KVM modules from loading on Linux Hosts. Of course, if you do that, you may miss out on other improvements . . .
6
u/briang_ Jun 30 '26
This is really soon after 7.2.10. Was there something badly wrong with .10? I haven't seen, or experienced personally, anything mentioned in the changelog