Making use of Linux’s Kernel-based Virtual Machine (KVM) opens up new possibilities while users can still enjoy the VirtualBox VMM itself. The KVM support is part of the mainline kernel so there is less worries with not having to use the VirtualBox kernel driver, KVM tends to support new features quite quickly, and tends to be more actively developed than VirtualBox and is embraced by a range of organizations. Early users of this backend by Cyberus customers are said to be experiencing better performance too.
Known issues and limitations
Currently, Intel x86_64 is the only supported host platform. AMD will most likely work too but is considered experimental at the moment. Linux is required as a host operating system for building and running VirtualBox KVM. Starting with Intel Tiger Lake (11th Gen Core processors) or newer, split lock detection must be turned off in the host system. This can be achieved using the Linux kernel command line parameter split_lock_detect=off or using the split_lock_mitigate sysctl.
Source: https://github.com/cyberus-technology/virtualbox-kvm
deleted by creator
Dumb question: why would anyone improve VBox?
I have heard of Oracle looking at IP addresses and if they notice a trend they try to collect a license off it. Same crap they do with Java. Do people use VBox and not concerned of Oracle looking over them?
I loved VBox back then, it worked great.
The performance of Virtual Box wasn’t even a contest vs KVM/QEMU. It’s easy to use, though VirtManager has gotten close to the ease of use that VB has.