top | item 44036699

(no title)

rizalp | 9 months 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.

discuss

dataflow|9 months ago

That makes no sense. Are you actually familiar with the technical issues or are you hand-waving? WSL2 itself is a Linux VM running in top of Hyper-V. Heck, as far as I know other Hyper-V VMs run fine alongside WSL2 too. Why can't a VirtualBox Linux VM do the same?

rizalp|9 months ago

Because Virtualbox and VMWare Workstation is Type-2 hypervisor, they run on top of the host OS (Windows), and not directly on hardware.

https://en.wikipedia.org/wiki/Hypervisor