If WSL v2 is running VM under the hood, no wonder it will be Hyper-V. We already have such lightweight VM for "Credential Guard/Device Guard" and it already conflicts will any other hypervisor: VMWare workstation [1], VirtualBox. Resolution is to disable Hyper-V, for instance, with command line
bcdedit /set hypervisorlaunchtype off
So most probably WSL v2 will do the same, which means one cannot run WSL v2 and non Hyper-V VMs at the same time, because two different hypervisors can't coexist.
If WSL v2 is running VM under the hood, no wonder it will be Hyper-V. We already have such lightweight VM for "Credential Guard/Device Guard" and it already conflicts will any other hypervisor: VMWare workstation [1], VirtualBox. Resolution is to disable Hyper-V, for instance, with command line
So most probably WSL v2 will do the same, which means one cannot run WSL v2 and non Hyper-V VMs at the same time, because two different hypervisors can't coexist.[1] https://kb.vmware.com/s/article/2146361