egpu-switcher VS gpu-passthrough-tutorial

If you're ok with running X11, you can use egpu-switcher and modify the Xorg configuration yourself afterwards.

Only using Xorg since Wayland gave me more issues than fixes. I'm using egpu-switcher

Try installing eGPU-switcher, make sure you have the right drivers installed, and as others have said make sure you have the right cable. Last thing, only plug in or unplug the eGPU when the laptop is off.

You didn't mention the problems you ran into but it should be plug and play. You will have to set up the proper config for it to work properly, and I would recommend using hertg's egpu-switcher if you are having issues: https://github.com/hertg/egpu-switcher

I've been using egpu-switcher every single time.

The scripts are all-ways-egpu for Wayland and egpu-switcher for X11.

here is the hotplug script that seemed promising, but did not work for me (nVIDIA only) here is a more sophisticated-looking script that seems intended for Desktop-users though, and also specifically excludes hotplugging options...

It is not plug&play, but almost. https://github.com/hertg/egpu-switcher

The A750 is now a recognized PCIe device, and works with connected displays to an extent. During boot, KMS/Plymouth shows on connected displays, as well as GDM (albeit, laggy, but it did that before anyways). The problem starts with Xorg, where during startx, I get a No screens found error. My Xorg configuration was autogenerated by egpu-switcher, where it only fails in egpu mode (connected displays do not work in internal mode). GNOME on Wayland works surprisingly with my laptop display working as normal, but the eGPU's external displays come with various graphical glitches, stuttering, outputting to 1080i30 on a 1440p60 display, etc.

Check https://github.com/bryansteiner/gpu-passthrough-tutorial. It looks like a well-written and comprehensive guide to set up GPU passthrough with KVM (Pop-OS specific). If you have spare external hard drives, just backup your OS through Clonezilla/Rescuezilla so that you can restore the OS if it breaks.

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

So bad news I followed this guide completely without luck I tried passing through my 5500 xt and it just shows a black screen and it also makes my main display which is using my Intel arc a770 gray as well

Hi, I've been trying to pass a AMD Radeon 6700 (non XT) to a Windows 10 VM following this guide. First of all, I haven't been able to get any output signal after turning the VM on, but also don't get a video signal after the VM stops and is supposed to reattach to the host. Trying to start the VM again yields a "Unknown PCI header type '127'" error. I have heard about the AMD reset bug, but I thought the issue was fixed with 6000 series cards.

Looks like your missing some optimizations such as hyperv enhancements and cpu pinning among others. Mine was quite laggy prior to the changes outlined Here

I am running Windows successfully with passing my Nvidia GPU to it. The setup was pretty easy and without any large issues. Hooked the GPU into the system using this tutorial and installed the drivers. It works nice with a monitor connected. It also works well with Looking Glass and games also run as expected.

I just stumbled upon a guide by Brainstenier on Github that explains how to use hook scripts to dynamically bind devices (GPU, SSD, etc.) to the Windows VM before launching it, and unbind them after shutting done the VM.

I used steps from [Bryan's tutorial](https://github.com/bryansteiner/gpu-passthrough-tutorial) and this OpenSUSE wiki page for setting up my VM.

I tried following https://github.com/bryansteiner/gpu-passthrough-tutorial but I couldn't get it to work. It would stall when the hook script fired to unbind the GPU. I scrapped it and am going to start over.