|
|
|
|
|
by rizalp
389 days ago
|
|
It's because WSL2 is using HyperV behind the scenes, and HyperV is a Type 1 (Native Hypervisor), running directly on top of hardware. When you activate it, it also makes you host windows OS virtualized as well, albeit with native access for some components like GPU etc. That's why all other Windows Hypervisor (Virtualbox, VMWare Workstation) will experience one issue or another when WSL2 is activated, because more abstraction is happening and more things could go wrong. |
|