4 ms·
Exactly my question. How confusing. Especially since there is some feature discrepancy between WSL1 and WSL2, sometimes there is a need to use the former.
by RaoulP 4y ago
Exactly my question. How confusing.
Especially since there is some feature discrepancy between WSL1 and WSL2, sometimes there is a need to use the former.
- andix 4y agoYep, WSL1 is good and sometimes very fast, it’s just not as compatible to linux as WSL 2.
- Brian_K_White 4y agoIt's more compatible if you want to access a usb or serial port. WSL2 is like a car that's great in most ways but for some reason just cannot make right turns from one-way streets. You might not encounter that particular situation very often but your car still needs to be able to do it or else it's just an annoying 3/4-baked thing that is better just skipped until it's actually fully functional.
- RaoulP 4y ago> It's more compatible if you want to access a usb or serial port. Yep, that's the case I had in mind.
- bravetraveler 4y agoI quite prefer the original, albeit little more than a container. Mostly because the newer version forces you into Hyper-V, and I'd rather not be committed to that hypervisor If I'm on Windows I'm much more likely to want good old VMWare Workstation. Enabling WSL2/Hyper-V precludes this I haven't had nearly as good of an interactive (UI capable) guest experience with anything else (beyond KVM with QXL/Spice) Edit: At risk of arguing their merits, video game anti-cheat clients will often categorically refuse to run if Hyper-V is enabled, too.
- yusefnapora 4y agoYou can run VMWare Workstation with Hyper-V enabled now: https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html https://blogs.vmware.com/workstation/2020/05/vmware-workstat...
- bravetraveler 4y agoAh, awesome! That's a good step, I'll give it a try the next time I find myself on Windows. I'm curious if the seemingly choppy display stuff continues, it has been quite a while. As much as it pains me, I have to avoid Hyper-V generally for anti-cheat client compatibility
- bpye 4y ago> As much as it pains me, I have to avoid Hyper-V generally for anti-cheat client compatibility Which anti cheat clients still have trouble with Hyper-V?
- bravetraveler 4y agoESEA is the one on my mind - service I participate w/ for CS:GO. Partner of ESL, leagues/practice on servers better than first party (128 tick vs 66) ref: https://support.esea.net/hc/en-us/articles/360008741974-Error-1006-1008-114-and-119-Hypervisor-launch-type-must-be-set-to-off-before-launching-the-ESEA-Client- https://support.esea.net/hc/en-us/articles/360008741974-Erro... There are others, I think Valorant complained... but I gave up when I couldn't mask it
- bravetraveler 4y agoTo expand (I can't edit now)... ESEA anti-cheat is posited as Hyper-V specific, but it's actually against being virtualized in general. I was able to work around this with KVM on Linux with a GPU passed to a Windows VM. I tweaked the libvirt XMLs (VM definitions) a few key ways and was able to convince ESEA it's bare metal, but not Valorant. I never got to play it, but it's fine by me :) This combination works well enough, I only boot up Windows when I need a couple anti-cheats I've managed to trick (that also can't work in Proton)