QuickPassthrough

A project to simplify setting up GPU passthrough on your Linux host for QuickEMU(vfio support not developed yet) and libvirt/virt-manager

You can use it by simply downloading the latest release and run it inside a terminal/shell or by downloading and compiling it yourself with the commands below.

git clone https://github.com/HikariKnight/quickpassthrough.git
cd quickpassthrough
go mod download
CGO_ENABLED=0 go build -o quickpassthrough cmd/main.go

How do I undo the changes?

There is a "backup/" folder generated on the first run that will have a copy of all your files (and their paths) from before we edited anything. Copy the files back to your system (blank files inside .d/ folders will be used to "undo" any new config files we wrote) and rebuild your initramfs then remove the kernel arguments listed in config/kernel_args from your bootloader (if your system use kernelstub, grubby or you had to manually add them).

How do I just disable vfio for 1 boot?

Remove the vfio kernel arguments from your bootloader by pressing E on the boot menu. The kernel arguments added to the bootloader can be found in the config/kernel_args file NOTE: You can also just remove them from your bootloader permanently and update your bootloader if you want to keep the config files on your system.

What this project does NOT do

Setup or configure your Virtual Machine (that is your job)
Optimize your Virtual Machine for Passthrough (again this is your job)
Optimize your host machine for Passthrough or Virtualization (out of this projects scope)
Setup and configure GPU Passthrough on systems with 1 graphic card (iGPU counts as 1 Graphic Card by itself, so iGPU with another GPU will work)
Does not configure passthrough of 3D controllers, as it will not work (this is most gaming laptops so do not even think about it). If you try run this on a laptop with a 3D controller, the "2nd GPU" will not show up. NOTE: This project is aimed at desktops

Features

Show general warning to user and inform about making a backup and general expectations
Detect if user has an amd or intel CPU and provide the correct IOMMU kernel args based on that
Configure your 2nd GPU for GPU Passthrough (1 for host, 1 for VM)
Use ls-iommu to find PCI devices like graphic cards, usb controllers, etc and see what IOMMU group they are in
Enable and configure vfio modules (initramfs-tools, dracut, modprobe and mkinitcpio)
Generate the correct kernel arguments for grub and systemd-boot
Generate a script to use for dumping the vbios rom (as some cards require a romfile for passthrough to work), however no rom patching support planned.
Configure kernel arguments for systemd-boot (using kernelstub or grubby)
Configure kernel arguments for grub2 (editing /etc/default/grub or using grubby)
A menu system you can navigate through, built using Bubble Tea (Help appreciated to make this menu better!)
~~Coloured highlight/text for important information?~~ (not implemented yet)
Make sure vendor-reset module is loaded before vfio, check the repository for the list of cards that require it!
Provides you with the correct kernel arguments to add to your bootloader entry if a supported bootloader is not found

Features now handled by ls-iommu

Automatically handle GPUs where parts of it might be in separate IOMMU groups (ex: RX6600XT)
Fetch the ID and PCI Address of devices
Locate the vbios rom path on the system
Tell the user to enable IOMMU (VT-d/AMD-v) on their motherboard and bootloader
Get a list of devices, their IOMMU groups and various other information

Contributing

This project originally started out as a bash only project, upon completing the proof of concept it became very clear that bash would become very messy with all the weird quirks and regex and inline editing of files.
So the project moved over to golang, this lets us utilize TUI toolkits like Bubble Tea to build a proper menu system for the project.

If you know golang, bubbletea, passthrough or qemu, you are welcome to help! Just make a pull request to the dev branch with your changes!
Just remember to add comments to document the work and explain it for people who are less familiar with the bash syntax or anything else you use. 😄

Also if you know English, you can help by just proof reading. English is not my native language, plus I have dyslexia so I often make spelling mistakes. Proof reading is still contribution!

Why GO?

I wanted to learn it, while also using a language that would potentially not create system dependencies. GO fits this criteria when you compile using CGO_ENABLED=0 as this will statically link the libraries and still produce a fairly small (when compressed with upx) binary.

5.3 KiB Raw Blame History