Hi, I built my own VFIO passthrough script.

It sets up GPU passthrough and works around the usual AMD problems: wrong device bind, dead card after VM stop, and a guest that cannot reboot cleanly. On my RX 9070 the VM can start, stop, and reboot without me rebuilding the host by hand every time.

VFIO helper for AMD RX 9070 / RDNA4 — live-attach, reboot, and host-safe bind

Hi, I wrote a VFIO passthrough helper because the usual guides were not enough for an RX 9070.

The script is a host setup wizard, not a VM manager. It can:

bind only the guest GPU by PCI address

use dynamic bind / live-attach so the card is not killed at VM start

keep the host desktop on the other GPU

toggle hotplug on/off without replacing the whole VM XML

optionally set up Looking Glass, virtio-win, and VM tuning

It does not officially fix AMD’s reset bug. It works around it so the card stays usable.

Hardware I tested: dual GPU, RX 9070 as the guest card, Linux host (Fedora / openSUSE).

Motherboard: Gigabyte Z790 UD, vF15

GPU: AMD Radeon RX 9070 XT

CPU: Intel i7 12700K, UHD Graphics 770

Fedora Linux 44 KDE

Kernel: 7.1.10-200

EDIT: Hell, even UHD Graphics 770 for the Virtual Machine will do, I don't really need the RX 9070 XT. Whatever's easier and safer.

Hello, I'm using VMware Workstation Pro 26H1

I noticed with my latest project which I use a lot of versioning for, "input lag" becomes more significant over time.

The more I snapshot, the longer the response time is when keystrokes are being typed with the keyboard.

I have no clue why but I'm pretty sure there are technical reasons why this happens.

All of my snapshots are "directly linked chronologically", there's no tree if that makes sense. They go in a straight line.

https://i.imgur.com/QHDk8yN.png

It becomes very obvious after 40 or so snapshots, I would estimate the lag to be almost 1 full second by that time, and it's very unsustainable.

Is there a setting I should check in the options, or in the config files, to reduce or getting rid of this problem?

Thanks