Easy-GPU-PV VS wslg

I'm trying to run the update "Update-VMGpuPartitionDriver.ps1" command mentioned in the instructions alongside with my VM and gpu name (which is auto) but it keeps telling me it doesn't recognize that command in both powershell and powershell ISE.

One nice thing about WSL: GPU "passthrough" (via GPU-PV) is handled out-of-the-box.

There are some solutions (such as https://github.com/jamesstringerparsec/Easy-GPU-PV) that makes the process easy if you are using Hyper-V as the hypervisor, but it is not a straightforward task yet. Hopefully that will change in the future!

Using Google Collab would be easier, but if you want to try partitioning GPUs, this might work: https://github.com/jamesstringerparsec/Easy-GPU-PV (No, I haven't tried it, so don't ask me any questions. ;-)

https://github.com/jamesstringerparsec/Easy-GPU-PV Proxmox would be a good option for this.

As far as I know, GPU virtualization (passthrough) is not featured by VirtualBox (was removed in version 6), so it won't let you pass through the GPU to the VM. However, Virtualbox provides 3D acceleration through Guest Additions, which accelerates some VM graphics by running them on the host (old games might run inside the VM). For GPU passthrough on a Windows host, you need to use Hyper-V. See Easy-GPU-P Github page: https://github.com/jamesstringerparsec/Easy-GPU-PV

Windows hosts do not allow PCIe passthrough, but instead use GPU-PV to partition GPU calls to a Windows VM. This GitHub may be helpful in that regard.

There are 3 major options Hyper-V, ESXi or KVM. If you want to you use VM for OBS, you might need to passthrough entire GPU to achieve better results. It is supported on all hypervisors (except Hyper-V on desktop Windows OS). r/vfIO should help with GPU passthrough on KVM. Check the following script for Hyper-V and GPU-P. https://github.com/jamesstringerparsec/Easy-GPU-PV/blob/main/Add-VMGpuPartitionAdapterFiles.psm1

WSLg(Windows Subsystem for Linux GUI) uses RDP and FreeRDP to work: https://github.com/microsoft/wslg

I haven't tried it yet, but I'm hopeful the experience is better than last time I tried Hyper-V enhanced linux experience. I imagine this use case is getting FreeRDP way more attention.

For years I've developed in a Linux VM on a Windows host via VirtualBox. The typing lag on this, particularly in IDEs like VSCode and Rider, finally got to me. So, I moved over to WSL and have to say; the experience is amazing.

This is running in WSL?

Microsoft has some wayland stuff already for WSL, though I think internally there's RDP involved: https://github.com/microsoft/wslg

That said. Graphical apps will just run on WSL without needing to install anything. Check: https://github.com/microsoft/wslg

What are you talking about? Its free forever https://github.com/microsoft/wslg

Actually, you can https://github.com/microsoft/wslg

See: https://github.com/microsoft/wslg/issues/563 and other similar issues on wslg GitHub.

Apparently, WSLg does away with the need for a separate X server, making things "easy" to use:

https://github.com/microsoft/wslg

There's two completely different aspects to your question. 1) How to manage libraries in c++ without dying from cringe? I'd suggest you use cmake as the build system and grab library sources directly from GitHub using this tool: https://github.com/cpm-cmake/CPM.cmake 2) How to get apps that run under WSL to display windows-native windows? I'm not sure, but it's probably this: https://github.com/microsoft/wslg

Here’s a thread about it. You can get into the underlying RDP session instead of just apps launching. https://github.com/microsoft/wslg/issues/1019