Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
b
best-city-49378
06/19/2022, 12:06 PMSame ole Hyper-V either way, but some people find this to be more exciting than VirtualBox
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.
In 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)
No 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
That 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
There is just so much missing from Windows, that I am thinking of only "supporting" MSYS (with MinGW and pacman).