This message was deleted.
# limaa
adamant-kite-43734
06/19/2022, 12:06 PMThis message was deleted.
f
fast-garage-66093
06/20/2022, 6:27 PMAre you saying qemu would still use hyper-v on Windows? In that case I think it will have the same issue with UNIX sockets as WSL2.
fast-garage-66093
06/20/2022, 6:28 PMIn addition you probably require Windows Professional for the Hyper-V license. Windows Home allows you to run WSL2 on Hyper-V, but not your own VMs.
b
best-city-49378
06/20/2022, 7:10 PMIt uses the same hyper-v framework, if I understand things correctly (WHPX)
best-city-49378
06/20/2022, 7:11 PMNo idea about licensing, only tried it on work computer
f
fast-garage-66093
06/20/2022, 7:17 PMI don't know for sure, but I think this means it won't work on Windows Home: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/hyper-v-requirements
fast-garage-66093
06/20/2022, 7:18 PMThat was one of the reason we choose WSL2 for Rancher Desktop (and I suspect was a reason for Docker Desktop as well)
b
best-city-49378
06/20/2022, 7:33 PMI think there are still valid reasons to continue to use WSL2, this QEMU-based experiment is more to use the same base
best-city-49378
06/20/2022, 7:34 PMThere is just so much missing from Windows, that I am thinking of only "supporting" MSYS (with MinGW and pacman).
2 Views