DaDesktop Nested Virtualization Compatibility
Getting nested virtualisation to work smoothly can be quite a challenge. Below you’ll find our recommendations on which virtualisation tools are suitable, or perform best, across the different environments inside DaDesktop.
Feel free to reach out if you have any questions. Note that some tools, such as Virt Manager, aren't available on every operating system.
Detailed information on using Virt Manager to set up multiple sandboxed servers and desktops is also provided.
| 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 |
|
Testing 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 |
Notes:
①: Intel VT-X and AMD virtualisation acceleration in the guest is not supported. You need to uncheck the "Virtualize Intel VT-x/EPT or AMD-V/RVI" checkbox under hardware processors.
②: The VirtualBox version on the guest must match the VirtualBox DKMS version installed on the host.
③: Running VirtualBox inside an LXC container conflicts with KVM virtual machines, so all KVM instances on the host must be stopped.
④: Encountered a soft lockup systemd-udevd error, causing sluggish, stuck behaviour.
