DaDesktop Nested Virtualization Compatibility
Getting nested virtualisation to run smoothly can be challenging, even in ideal conditions. Below you’ll find our guidance on which virtualisation tools perform well—or deliver the best results—across the different setups inside DaDesktop.
Do reach out if you have any questions. Please note that certain tools, such as Virt Manager, aren’t offered on every operating system.
You can also read more about using Virt Manager to spin up multiple sandboxed servers 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 isn’t supported inside the guest. You’ll need to untick the “Virtualize Intel VT-x/EPT or AMD-V/RVI” option under hardware-processors.
②: The VirtualBox version on the guest must match the VirtualBox DKMS version on the host.
③: Running VirtualBox inside an LXC container clashes with active KVM virtual machines, so you must stop all KVM instances on the host first.
④: We encountered a soft lockup with the systemd-udevd error, causing sluggish performance and occasional hangs.