Watch Out: Microsoft Windows WSL1 Currently Borked With Ubuntu 20.04

[bug77]

Curious if anyone knows the answer to this: If I understand correctly, WSL2 uses it's own Linux kernel in virtualization, vs. just being a Linux systems call to NT kernel call translation layer as in WSL1. WSL2 is supposed to use Hyper-V as the virtualization. And (again), if I remember correctly, running/enabling Hyper-V blocks the ability to run VirtualBox, at least I think I remember that experience. Does anyone know if you can run WSL2 and VirtualBox together? Doesn't need to be at the same time, I just don't want installing WSL2 to block VirtualBox usage. Maybe WSL2 just runs Hyper-V 'as needed' then goes away otherwise. Maybe I can play with this to figure out, but yeah, don't run insider builds for now. Since I am going to do a clean wipe install after spring release (yes, I also run Windows - what I traitor I am!), I might enable the insider build for now and see what happens.

A simple search will answer that: https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq

More OT, with WSL2 available, I wouldn't give WSL1 another thought.

[Vorpal]

Does anyone know if people actually use WSL, and if so for what? I assume so, since Microsoft considers it worthwhile to continue to support it. I have a Windows partition for the occasional gaming, and out of interest I tried WSL1 there a few months ago. I found the experience slow and lack-luster, to the point of preferring Cygwin if I have to use a terminal on windows, and that is saying something! Maybe this has changed with WSL2, but even then I don't believe GUI programs are supported.

As a result, I struggle to see who this is for. I have seen some vague suggestions it is for software developers, who need Linux to build stuff, but would prefer (or who's IT departments prefer) to work in Windows. Maybe this is true for some fields, but as a software developer in the field of robotics, the lack of GUI support (with proper 3D acceleration) is crippling.

[ehansin]

Curious if anyone knows the answer to this: If I understand correctly, WSL2 uses it's own Linux kernel in virtualization, vs. just being a Linux systems call to NT kernel call translation layer as in WSL1. WSL2 is supposed to use Hyper-V as the virtualization. And (again), if I remember correctly, running/enabling Hyper-V blocks the ability to run VirtualBox, at least I think I remember that experience. Does anyone know if you can run WSL2 and VirtualBox together? Doesn't need to be at the same time, I just don't want installing WSL2 to block VirtualBox usage. Maybe WSL2 just runs Hyper-V 'as needed' then goes away otherwise. Maybe I can play with this to figure out, but yeah, don't run insider builds for now. Since I am going to do a clean wipe install after spring release (yes, I also run Windows - what I traitor I am!), I might enable the insider build for now and see what happens.

[tildearrow]

Typo:

With the updated GNU C LIbrary

[CommunityMember]

"Upgrading" to WSL2 is not quite that easy for some, since you have to be on a Windows 10 Insider build as of now, although the Windows 10 2004 (aka 20H1) GA release is expected RSN which should make WSL2 generally available.

[phoronix]

Phoronix: Watch Out: Microsoft Windows WSL1 Currently Borked With Ubuntu 20.04

A public service announcement was issued with Windows Subsystem for Linux (WSL) currently will have issues in running Ubuntu 20.04 LTS so users should either wait for Microsoft to release a fix, upgrade to WSL2, or stick to using the older Ubuntu 18.04 LTS instead...

http://www.phoronix.com/scan.php?page=news_item&px=WSL1-Breaking-Ubuntu-20.04