Changes have been added to the VirtualBox virtualization system repository to enable the use of the built-in kernel Linux The KVM hypervisor replaces the specific VirtualBox kernel module (vboxdrv). The implementation was developed by Oracle employees and is developed separately from the VirtualBox-KVM patch set maintained by Cyberus Technology. Oracle began working on the KVM backend several years ago, but its development was delayed due to a lack of engineering resources.
As of commit 5cb05ca, the backend KVM It's more or less in working order, at least for more modern guest systems. Older and more exotic operating systems, such as MS-DOS, are not yet supported or tested. If VirtualBox can't access native kernel drivers, it will fall back to KVM if available. Saved states between the native hypervisor and KVM should be compatible. There are no test builds yet, and the code is only available in the current GIT snapshot.
The implemented backend will solve issues with running VirtualBox on distributions with UEFI Secure Boot support, such as Fedora and RHEL, which refuse to sign third-party drivers. KVM support will also allow VirtualBox to run in Linux- on systems not yet supported by the vboxdrv driver, use VirtualBox concurrently with other KVM-based virtualization systems and utilize advanced hardware-accelerated virtualization mechanisms supported by KVM but not used by VirtualBox (for example, the APICv extension for interrupt controller virtualization).
Source: opennet.ru
