DaDesktop Nested Virtualization Compatibility
Getting nested virtualisation to perform smoothly can be challenging, even under ideal conditions. We’ve outlined which virtualisation tools function—or deliver the best results—in each environment within DaDesktop.
Reach out if you have questions. Keep in mind that some tools, such as Virt Manager, aren’t offered on every operating system.
You can also explore more details about using Virt Manager to supply multiple 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 virtualisation acceleration inside the guest isn’t supported. You’ll need to uncheck the "Virtualize Intel VT-x/EPT or AMD-V/RVI" option found under hardware-processors.
②: The VirtualBox version running on the guest must match the VirtualBox DKMS version installed on the host.
③: Operating VirtualBox inside LXC clashes with active KVM virtual machines, so all KVM instances on the host have to be stopped first.
④: We saw a soft lockup systemd-udevd error, resulting in sluggishness and freezing.