The best part of Windows 11 is a revamped Windows Subsystem for Linux

One of the most repeated questions we’ve seen about WSLg can be expressed as “why bother?” This is because the majority of GUI “killer apps” in the Linux world aren’t really Linux-specific—the vast majority have already been ported directly to the Windows platform. And for those apps, running the native Windows ports frequently makes more sense.

With that said, there is one obvious “killer app” for WSLg that has us excited—and that’s virt-manager, the RedHat-originated virtualization management tool. virt-manager is a simple tool that streamlines the creation, management, and operation of virtual machines using the Linux Kernel Virtual Machine.

With virt-manager, you can see a simple list of your VMs along with how much disk, network, and CPU activity is currently associated with each. You can also manipulate their virtual “hardware”—e.g., by adding or removing RAM, “disks”, network interfaces, and more—and start, pause, or stop them. Creation and destruction of VMs is as easy as management—and, finally, virt-manager allows you to pull a graphical console directly into each VM, which behaves just as a physical display connected to a bare-metal machine would.

If all of this only worked on the local host, it would be pretty useless under WSLg. Nested virtualization is a thing, but it’s generally not something you want to do in production. However, virt-manager allows you to manage the VMs on any machine you can SSH to, not just the local host. In practice, I use this remote management feature to manage many tens of hosts (and a few thousand VMs), both local and remote, on a day-to-day basis.

But…

Unfortunately, virt-manager never got a Windows port and seems unlikely to. But it runs under WSLg like a champ. In the screenshots above, you can see my Framework laptop running virt-manager under WSLg, connected via SSH to my Ubuntu workstation. The Ubuntu workstation has a variety of VMs installed and running—and virt-manager on my Framework laptop can manage them all, including the Hackintosh VM and Windows Server 2012 R2 VM it has console windows open to.

The cherry on top of this virtualization cake is just how well those console windows work—I had no trouble getting flawless YouTube playback on my Hackintosh VM console, complete with working, glitch-free audio. Ironically, this is a better remote control experience than I can manage with my real Macbook Air—which is unbearable to use for so much as spreadsheet work, thanks to it being limited to VNC over Wi-Fi.

What can’t I do with WSLg on Windows 11?

As much as we’re loving the enhanced Windows Subsystem for Linux functionality in Windows 11, it’s still not quite a “real” Linux VM.

As far as I can tell, there’s still no networking bridge mode—which means it’s difficult to run a network server application (Apache, Nginx, MySQL, Samba, etc) on your WSLg guest and expose its services to other machines on the network. This self-described “hilariously unsupported, unapproved, and experimental” workaround still seems to be the closest thing to a real network bridge available—which sharply limits the usability of WSL-based application servers.

You can’t run GNOME’s Software Center app under WSLg—more accurately, you can install and run it, but it’s effectively useless. We’re not sure exactly what goes wrong with Software Center, but it pops a “failed to connect to upower” error on the console and fails to list any available applications. It also didn’t list all of our installed applications! This is a shame, as it otherwise would have been a nice way for Windows-using Linux newbies to browse the software available for their new WSLg distribution.

You also can’t run the GNOME shell desktop environment itself under WSLg. Running apt install gnome-shell works fine and pulls in the enormous list of dependencies necessary to satisfy that request—but gnome-shell itself fails ignominiously with unsupported session type, which effectively means it doesn’t like WSLg’s Weston/XWayland environment.

ZFS

Finally, Ubuntu’s excellent baked-in OpenZFS support is missing. You can apt install zfsutils-linux without difficulty, but that package depends on Canonical’s in-house kernel with built-in ZFS support, which Microsoft has not picked up in its own WSL2 kernel.

Determined Ubuntu users can still apt install zfs-fuse and expect that user-mode implementation to work as well as it does under native Ubuntu—but we don’t recommend it for production; the FUSE implementation is still stuck on 0.7.0, while the in-kernel version is 0.8.3. This means a lack of support for ZFS-native encryption, along with a whole host of other features, bug fixes, and enhancements—let alone the performance implications of running under FUSE rather than in-kernel.

We did not test DKMS-based implementations of in-kernel ZFS, such as those typically used in RHEL-based distros.

Conclusion

If you’re already a Windows Subsystem for Linux (WSL) user, Windows 11 offers an enormously improved experience compared to what you’re accustomed to from Windows 10. It installs more easily, makes more functionality available, and offers better desktop integration than older workarounds such as running MobaXTerm‘s X11 server.

As a diehard desktop Linux user myself, the new WSLg functionality is nowhere near enough to make me consider going back to Windows on the desktop. But it does eliminate a lot of pain points for fellow Linux users “trapped” in Windows-land at work, as well as offering the easiest way possible for newbies to get their feet wet and try new things.

We especially appreciate Microsoft’s forward-thinking approach in standardizing on Weston/Wayland rather than an X server—and the company’s apparent determination to really integrate it properly with the open source stack traditional desktop Linuxes are based on.

If you’re still on the fence about whether or when to bother with a Windows 11 upgrade, its new and improved WSL just might be the best reason yet to go ahead and take the plunge now.