gonzodaruler

*

1 point by gonzodaruler 0 minutes ago | next | edit | delete [–]

> Of course, some day Virtualbox may support a KVM backend, just as virtualization tools are starting to support unified hypervisor backends on Windows and macOS. There's even an existing patch, though I do not know what the status is and whether or not it could ever be merged upstream.[3]

This is the official patch set for the VirtualBox KVM backend. Our plan is to support this for the near future. There are even packages for ArchLinux (AUR), gentoo and NixOS already if you want to test this.

Since version 7.0, VirtualBox supports the NEM (Native Execution Manager) mode for other hypervisors. With the NEM, basically all hypervisors can be supported as backend.

This is definitively not expected. You could also try setting the CPU/Mem configuration via VBoxManage. Maybe you get a good error message then.

`VBoxManage modifyvm <vm_name> --cpus <number of cpus>`

`VBoxManage modifyvm <vm_name> --memory <amout of memory in MB>`

A lot of this has changed in recent VirtualBox versions. USB3 and Webcam support is now part of the OSE release.

Thanks. You can indeed use the extension pack with KVM Virtualbox, just make sure that you don't violate any license agreements.

The emulated hardware is basically the same as with stock VirtualBox. Only the interrupt contoller (local APIC) is emulated by KVM.

You can use `VBoxManage --attach-vfio` if you want to experiment with pci passthrough. This is different from the Oracle `pciattach` call and does not require any support from the extension package.