vanities/gpu-passthrough-arch-linux-to-windows10

GPU Passthrough and virt-manager walkthrough

GPU Passthrough from Arch Linux

Issues

If you have any issues with these steps please hit me up and I will try to fix them!

Combines these sources:

1. https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF

2. https://passthroughpo.st/quick-dirty-arch-passthrough-guide/

3. https://medium.com/@dubistkomisch/gaming-on-arch-linux-and-windows-10-with-vfio-iommu-gpu-passthrough-7c395dde5c2

4. https://pastebin.com/wetAhhVX

When to do this:

When you want to play windows 10 video games from your arch box because:

1. wangblows and you have access to a windows 10 iso

2. you don't want to read mountains of text because you just want to play gaems.

Required downloads:

1. a Windows 10 installation iso

Link: here

Direct Download: here

2. virtio* drivers for windows10

Link: here

Direct Download: here

Disclamer:

Most of this stuff is in the archlinux guide at the top, read more of that if any of this is confusing or something terribly goes wrong. This is my rig:

---

PCI passthrough via OVMF (GPU)

Initialization

1. Make sure that you have already enabled IOMMU via AMD-Vi or Intel Vt-d in your motherboard's BIOS HIT F10 or del or whatever the key is for your motherboard during bios initialization at beginning of startup, enable either VT-d if you have an Intel CPU or AMD-vi if you have an AMD CPU

2. edit /etc/default/grub and add intel_iommu=on to GRUB_CMDLINE_LINUX_DEFAULT

$ sudo nvim /etc/default/grub For Intel:

GRUB_CMDLINE_LINUX_DEFAULT="quiet ... intel_iommu=on"

For AMD:

GRUB_CMDLINE_LINUX_DEFAULT="quiet ... amd_iommu=on"

3. re-configure your grub:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

4. reboot

$ sudo reboot now

Isolating the GPU

One of the first things you will want to do is isolate your GPU. The goal of this is to prevent the Linux kernel from loading drivers that would take control of the GPU. Because of this, it is necessary to have two GPUs installed and functional within your system. One will be used for interacting with your Linux host (just like normal), and the other will be passed-through to your Windows guest. In the past, this had to be achieved through using a driver called pci-stub. While it is still possible to do so, it is older and holds no advantage over its successor –vfio-pci.

1. find the device ID of the GPU that will be passed through by running lscpi

$ lspci -nn

and look through the given output until you find your desired GPU, they're bold in this case:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1)

Configuring vfio-pci and Regenerating your Initramfs

Next, we need to instruct vfio-pci to target the device in question through the ID numbers gathered above.

1. edit /etc/modprobe.d/vfio.conf file and adding the following line with your ids from the last step above:

options vfio-pci ids=10de:13c0,10de:0fbb

Next, we will need to ensure that vfio-pci is loaded before other graphics drivers.

2. edit /etc/mkinitcpio.conf. At the very top of your file you should see a section titled MODULES. Towards the bottom of this section you should see the uncommented line: MODULES= . Add the in the following order before any other drivers (nouveau, radeon, nvidia, etc) which may be listed: vfio vfio_iommu_type1 vfio_pci vfio_virqfd. The line should look like the following:

MODULES="vfio vfio_iommu_type1 vfio_pci vfio_virqfd nouveau"

In the same file, also add modconf to the HOOKS line:

HOOKS="modconf"

3. rebuild initramfs.

mkinitcpio -g /boot/linux-custom.img

4. reboot $ sudo reboot now

Checking whether it worked

1. check pci devices:

$ lspci -nnk

Find your GPU and ensure that under “Kernel driver in use:” vfio-pci is displayed:

1:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 980] [1462:3177]
	Kernel driver in use: vfio-pci
	Kernel modules: nouveau
01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 High Definition Audio Controller [1462:3177]
	Kernel driver in use: vfio-pci
	Kernel modules: snd_hda_intel

2. ???
3. profit

---

Configuring OVMF and Running libvirt

1. download libvirt, virt-manager, ovmf, and qemu (these are all available in the AUR). OVMF is an open-source UEFI firmware designed for KVM and QEMU virtual machines. ovmf may be omitted if your hardware does not support it, or if you would prefer to use SeaBIOS. However, configuring it is very simple and typically worth the effort.

sudo pacman -S libvirt virt-manager ovmf qemu

2. edit /etc/libvirt/qemu.conf and add the path to your OVMF firmware image:

nvram = ["/usr/share/ovmf/ovmf_code_x64.bin:/usr/share/ovmf/ovmf_vars_x64.bin"]

3. start and enable both libvirtd and its logger, virtlogd.socket in systemd if you use a different init system, substitute it's commands in for systmectl start

$ sudo systemctl start libvirtd.service 
$ sudo systemctl start virtlogd.socket
$ sudo systemctl enable libvirtd.service
$ sudo systemctl enable virtlogd.socket

With libvirt running, and your GPU bound, you are now prepared to open up virt-manager and begin configuring your virtual machine.

---

virt-manager, a GUI for managing virtual machines

setting up virt-manager

virt-manager has a fairly comprehensive and intuitive GUI, so you should have little trouble getting your Windows guest up and running.

1. download virt-manager

$ sudo pacman -S virt-manager

2. add yourself to the libvirt group (replace vanities with your username)

$ sudo usermod -a -G libvirt vanities

3. launch virt-manager

$ virt-manager &

4. when the VM creation wizard asks you to name your VM (final step before clicking "Finish"), check the "Customize before install" checkbox.

5. in the "Overview" section, set your firmware to "UEFI". If the option is grayed out, make sure that you have correctly specified the location of your firmware in /etc/libvirt/qemu.conf and restart libvirtd.service by running sudo systemctl restart libvirtd

6. in the "CPUs" section, change your CPU model to "host-passthrough". If it is not in the list, you will have to type it by hand. This will ensure that your CPU is detected properly, since it causes libvirt to expose your CPU capabilities exactly as they are instead of only those it recognizes (which is the preferred default behavior to make CPU behavior easier to reproduce). Without it, some applications may complain about your CPU being of an unknown model.

7. go into "Add Hardware" and add a Controller for SCSI drives of the "VirtIO SCSI" model.

8. then change the default IDE disk for a SCSI disk, which will bind to said controller.

a. windows VMs will not recognize those drives by default, so you need to download the ISO containing the drivers from here and add an SATA CD-ROM storage device linking to said ISO, otherwise you will not be able to get Windows to recognize it during the installation process.

9. make sure there is another SATA CD-ROM device that is handling your windows10 iso from the top links.

10. setup your GPU, navigate to the “Add Hardware” section and select both the GPU and its sound device that was isolated previously in the PCI tab

11. lastly, attach your usb keyboard

12. don't forget to pass some good RAM as well

installing windows

1. test to see if it works by pressing the play button after configuring your VM and install windows

You may see this screen, just type exit and bo to the BIOs screen.

From the BIOs screen, select and enter the Boot Manager

Lastly, pick one of the DVD-ROM ones from these menus

2. from here, you should be able to see windows 10 booting up, we need to load the virtio-scsi drivers

When you get to Windows Setup click Custom: Install windows only (advanced)

You should notice that our SCSI hard drive hasn't been detected yet, click Load driver

Select the correct CD-ROM labled virto-win-XXXXX**

Finally, select the amd64 architecture

3. your SCSI hard drive device should be there and you should be able to contiune the windows10 install

---

Performance Tuning

Check out my virth xml file

CPU pinnging

CPU topology

1. check your cpu topology by running

lscpu -e

editing virsh

edit by running something similar with your desired editor and VM name:

sudo EDITOR=nvim virsh edit win10

if this doesn't work, check your VM name:

sudo virsh list

your virsh config file should look something like this if your cpu is like mine, otherwise revert to the arch guide: cpu-pinning guide

enabling hugepages

1. edit /etc/default/grub

$ sudo nvim /etc/default/grub

2. add hugepages=2048 to GRUB_COMMAND_LINE_DEFAULT

your final grub should look like this:

3. re-configure your grub:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

4. reboot and test it out

gpu-passthrough-arch-linux-to-windows10's Issues

OVMF Firmware Image Location

The /usr/share/ovmf/ovmf_code_x64.bin and /usr/share/ovmf/ovmf_vars_x64.bin have moved

I've yet to test a symlink but will update with my results.

GPU doesn't seem to work

I managed to complete the whole process, my 1080ti is visible inside the VM, I installed the Nvidia drivers, but still, under device manager, GPU has an exclamation mark and does not work.

The monitor that is connected to the GPU, is displaying some BIOS/POST info, and then freezes, while the VM runs in a small window with a Microsoft display adapter.

VM halt instant after starting

Hi, firt of all thanks for the instructions!

i followed your instructions exactly and the GPU i wanted to isolate (AMD Rx 480) could also be isolated, but when i try to start the VM with PCI passthrough the VM stops immediately and my second monitor on which the VM should be displayed stays black.

i hope you can help me

Linux session closes

But the session in Linux closes, What is the point or difference between this and dual-boot???

followed guide. kernel driver still shows this

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1)
Subsystem: Hewlett-Packard Company Device [103c:85fc]
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:10fa] (rev a1)
Subsystem: Hewlett-Packard Company Device [103c:85fc]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

Will I be able to use the gpu while not using the VM?

Not an issue. Just a question. I have read other tutorials that state that I am not going to be able to use the gpu if the vm is not in use. Is this true if I follow this tutorial?