DaDesktop Nested Virtualization Compatibility
Getting Nested Virtualisation to run smoothly isn't always straightforward. Below you'll find our guidance on which virtualisation tools function, or perform best, across different environments in DaDesktop.
Don't hesitate to get in touch if you have any questions. Bear in mind that some tools, like Virt Manager, aren't offered on every operating system.
You can also find more details on using Virt Manager to deliver several sandboxed servers and/or desktops.
| Intel CPU | AMD CPU | ||||
| KVM | LXC | KVM | LXC | ||
| Virt-Manager | Windows | N/A | N/A | N/A | N/A |
| Linux | √ | √ | √ | √ | |
| VirtualBox | Windows | √ | N/A | X④ | N/A |
| Linux | √ | √②③ | X④ | √②③ | |
| VMware Workstation | Windows | √① | N/A | √ | N/A |
| Linux | √① | X | √ |
X |
|
Test environment:
| Intel CPU Model: Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz | |||||
| AMD CPU Model: AMD EPYC 7502P 32-Core Processor | |||||
| Window: Windows 10 | |||||
| Linux: Ubuntu 20.04 | |||||
| Virtualbox: 6.1.18 | |||||
| VMware Workstation: 16 Pro, v16.1.1 |
Comments:
①: Intel VT-X & AMD virtualization acceleration in guest is not supported. You must uncheck the "Virtualize Intel VT-x/EPT or AMD-V/RVI" option in the hardware-processors settings.
②: The VirtualBox version on the guest must match the VirtualBox DKMS version on the host.
③: Operating VirtualBox in an LXC container will collide with active KVM virtual machines. Consequently, you need to halt all KVM instances on the host.
④: Encountered a soft lockup systemd-udevd error, resulting in sluggishness and a stuck state.