single-gpu-passthrough VS barrier

The main guides I have used are the bryansteiner guide, the risingprismtv guide and this Ubuntu 22.04 guide.

I am following this guide to achieve Single-GPU passthrough. I am stuck at step 5, because when I run the VM for the first time to install Windows, instead it shows me a black screen with "TianoCore" when I press a key to boot the CD-ROM drive.

Not long ago I setup single GPU pass through following the instructions the risingprism wiki (https://gitlab.com/risingprismtv/single-gpu-passthrough). This all went very smoothly and works great.

Try this one by rising prisim

Link: https://gitlab.com/risingprismtv/single-gpu-passthrough/-/issues/29

I just finished the coveted RisingPrism guide for Single GPU-Passthrough for a Windows 11 VM, and while I was successful for the most part, it wasn't entirely smooth.

Refer this guide https://gitlab.com/risingprismtv/single-gpu-passthrough/-/wikis/home for single gpu passthrough if ur concerned about gaming in linux

i basically followed this guide to a tee, and for some reason whenever i try booting into the VM, all i get is a black screen with my cursor. is there anything i can do to fix this?

Okay so issue, and how this all kind of ties together. I followed a siggle pass trough guide (https://gitlab.com/risingprismtv/single-gpu-passthrough/-/wikis/home) and I got the log which I replied to this comment which prompted me to do the ACS override pacth which didnt work and then I came here after I tried some other stuff. Back to the present I'm not sure how to fix this issue now (decided to restart over) , so in step 3 (IOMMU groups) It said to skip steps 8 and 9 if my devices were in 2 different groups, so i did, and now i get this.

I followed Risingprism's guide to Single GPU Passthrough. Currently though, disk usage is slow for me. The system often hangs when moving files around, and I can't move two files at the same time or else none of them get moved, I have to pause one.

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.