|
I think they still introduce small problems for people who run software they don't like. For example, if you run Linux on your desktop, and want to use a Windows VM for work, you can't run WSL2 or Hyper-V in the KVM/Qemu guest, even if nested virtualization is enabled and working with other operating systems. It used to work, but now it doesn't, and no know knows exactly why. These situations are murky. I don't know that they broke it deliberately. Maybe it broke on its own and the problem affects so few people that they just don't care about it. And you can't really demand that they spend their developer resources on things that they think won't help them. But on one hand, they wrote their own Wayland server for Windows 11, but on the other hand, they say, we can't make Teams work on Wayland. They do lots of odd stuff. It's pretty easy, and pleasant, to run a headless linux server on Hyper-V, but setting up a proper desktop system on your own is hard. They don't actually create a wall you can't get around, but they create obstacles that make it easier to do the things they want you to do. It's not fair or reasonable to get mad at them about this stuff. It's more that we should be clear about where they're coming from. |
Ubuntu 22.04 Host, virt-manager/ qemu/ kvm hypervisor Win10x64 Guest, CPU model is set to "Broadwell-noTSX-IBRS"
It's definitely not as performant with this setting, but it gets the job done so I can run WSL2 and Docker Desktop in my Windows vm.
YMMV.