A recent development in the VirtualBox source tree introduces an early but usable KVM backend for Linux hosts. According to a comment by contributor Alexander Eichner, the new backend is now in a workable state, or at least when running modern guest operating systems. Older or more unusual guests, such as DOS, have not yet been tested.
And if you’re wondering what benefits this brings, the main one is that having a KVM backend allows VirtualBox to continue running virtual machines even when its own kernel modules (vboxdrv, vboxnetflt, vboxnetflt, vboxnetflt) cannot be loaded.
This is especially relevant on modern Linux systems, where Secure Boot, kernel hardening, or distribution-specific policies can block third-party kernel drivers. In such cases, VirtualBox will now automatically fall back to using KVM if it is available on the host system.
Isn’t VirtualBox an Oracle property now? Fuck VirtualBox.
Came here to say that
Had been for over a decade and a half. There’s no reason to use that piece of garbage over virt-manager.
Came to ask whether someone uses this.
Even Window’s Hyper-V is better than virtualbox
So, VirtualBox is just a frontend for KVM? Why even use it at all then and not just libvirt with virt-manager?
Known interface and automation apis?
Automation APIs?? When the other option is libvirt? You can’t be serious.
Well, if you already have this stuff for VirtualBox? Not saying it’s good.
