Easy-GPU-PV VS barrier

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

For software KVM you can use https://github.com/debauchee/barrier

I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)

libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?

For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through

And for host systems, it looks like xev only logs input events when the window is focused.

Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?

With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.

Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier

libei:

I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.

Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...

Barrier appears to handle PC switching only for the keyboard and mouse.

Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.

Barrier is a free and open source alternative.