3 ms·

It works well enough for me to not worry about dual booting. Windows tends to claim some of the GPU memory - about 1.5GB on my 3090. If I do anything performanc

It works well enough for me to not worry about dual booting. Windows tends to claim some of the GPU memory - about 1.5GB on my 3090. If I do anything performance sensitive I’ll still do it in the cloud - but it has made my gaming/flight simulator PC massively more useful. You can also set up a network so your WSL2 installation shows up on your network as another host. Which is nice. Docker and docker with CUDA are a breeze too. Overall, I’m pretty happy with WSL2, but realize there are some performance drawbacks - so if my machine wasn’t massively overspec’d, I’d be much more concerned.

indigodaddy 4y ago
Is there any official doc for the network/bridged setup? Wasn’t aware that was possible..
- pridkett 4y ago
  It was a haul and I'm realizing now that I don't have it properly documented in my notes. But, that was a haul over the course of a couple years that had me experimenting with external USB network cards, virtual switches, and more. It's gotten way easier now. In your .wslconfig you'll want something like this: [wsl2] memory=48GB localhostforwarding=true networkingMode=bridged vmSwitch=WSL_external The key things are "networkingMode=bridged" and "vmSwitch=WSL_external". Then, open up Hyper-V manager on Windows, go to "Virtual Switch Manager" and create a new virtual switch using your primary ethernet adapter (I could never get this to work with my USB ethernet adapter). Check the boxed for "External Network" and "Allow management operating system to share this network adapter" and finally call it "WSL_external". That should do it for you. Incidentally, the port forwarding with WSL2 and Docker, has made this not entirely necessary, but I still like being able to SSH directly into my WSL2 host, not having to manage Windows' firewall rules, and being able to forward UDP for things like Mosh.
deleted 4y ago
[deleted]

indigodaddy 4y ago

Is there any official doc for the network/bridged setup? Wasn’t aware that was possible..

pridkett 4y ago
It was a haul and I'm realizing now that I don't have it properly documented in my notes. But, that was a haul over the course of a couple years that had me experimenting with external USB network cards, virtual switches, and more. It's gotten way easier now. In your .wslconfig you'll want something like this: [wsl2] memory=48GB localhostforwarding=true networkingMode=bridged vmSwitch=WSL_external The key things are "networkingMode=bridged" and "vmSwitch=WSL_external". Then, open up Hyper-V manager on Windows, go to "Virtual Switch Manager" and create a new virtual switch using your primary ethernet adapter (I could never get this to work with my USB ethernet adapter). Check the boxed for "External Network" and "Allow management operating system to share this network adapter" and finally call it "WSL_external". That should do it for you. Incidentally, the port forwarding with WSL2 and Docker, has made this not entirely necessary, but I still like being able to SSH directly into my WSL2 host, not having to manage Windows' firewall rules, and being able to forward UDP for things like Mosh.

deleted 4y ago

[deleted]