Archives
/
vfio-guide-2
mirror of https://gitlab.com/YuriAlek/vfio
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
personal
master
testing
testing-auto
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e351494e93'
${ noResults }
vfio-guide-2/README.md

9.5 KiB
Raw Blame History

Single GPU passthrough with QEMU and VFIO

![Windows 10 1709](/Screenshots/Windows 10 QEMU single GPU info.png)Windows 10 1709

Table of Contents

  1. What this does
  2. What you need
  3. My system
  4. vBIOS
  5. Configure
  6. Known problems
  7. TODO

What this does

In one command it kills X, frees the GPU from drivers and console, detaches the GPU from the host, starts the VM with the GPU, waits until the VM is off, reattaches the GPU to the host and starts lightdm.

What you need

  • An IOMMU enabled motherboard. Check your motherboard manual.
  • CPU support for AMD-v/VT-x and AMD-Vi/VT-d (AMD/Intel). And virtualization support enabled on BIOS.
  • One GPU that supports UEFI and its BIOS. All GPUs from 2012 and later should support this. If the GPU does not support UEFI you may be able to make it work, but you wont see anything in the screen until the drivers inside Windows kick in.
  • QEMU, OVMF UEFI and VIRTIO drivers for Windows.
  • [Optional] HDD only for Windows
  • [Recommended] Another computer to login remotely with ssh for convenience, at least until you have everything working.

My system

                                                [Hardware]
                                                 CPU: AMD Ryzen 5 2600
                                         Motherboard: Gigabyte AB350M-Gaming 3 rev1.1
                                    Motherboard BIOS: F23d
                                                 RAM: 16GB
                                                 GPU: Gigabyte Nvidia GeForce GTX 770
                                           GPU model: GV-N770OC-2GD
                                            GPU BIOS: 80.04.C3.00.0F
                                        GPU codename: GK104

                                                [Software]
                                        Linux Distro: ArchLinux
                                        Linux Kernel: 4.17.14 vanilla
                                       Nvidia divers: 396.51-1
                                        QEMU version: 2.12.1-1
                                        OVMF version: r24021

                                                 [Guests]
                                             Windows: Windows 10 Pro 1709 x64
                                               MacOS: MacOS High Sierra 10.13.3

vBIOS

I experienced some weird things when doing this on the display, like a corruption of the image, but seems to work fine. If you encounter anything, a reboot solved my problems.

Method 1 Linux

It did not work for me, the ROM is 59KiB and it should be around 162KiB. It may work for you.

  1. Execute scripts/iommu.sh as root to get the BUS ID for the GPU. Looks like 0000:06:00.0.
  2. Edit scripts/extract-vbios-linux.sh to your convenience. Change videobusid=. [Optional] Change also the location where the vBIOS will be save VBIOS=.
  3. Make the script executable with chmod +x scripts/extract-vbios-linux.sh
  4. Link the service to systemd: ln -s scripts/qemu@.service /usr/lib/systemd/system/
  5. Execute the systemd unit with sudo systemctl start qemu@extract-vbios-linux.service. You can also do it over ssh. The extracted ROM will be in the root directory /root/vBIOS.rom

From here you are alone, I don't know how to proceed. Maybe you need to edit, maybe don't.

Method 2 nvflash in Linux

  1. Download nvflash https://www.techpowerup.com/download/nvidia-nvflash/. Do not install from AUR; the package it's broken.
  2. Unzip it as /root/nvflash_linux with # unzip nvflash_5.414.0_linux.zip -d /root/
  3. Edit scripts/extract-vbios-nvflash.sh. Change videobusid with your GPU; NVFLASH= if you changed the location of the executable; and VBIOS= if you want the ROM in other place.
  4. Link the service to systemd: ln -s scripts/qemu@.service /usr/lib/systemd/system/
  5. Execute the systemd unit with sudo systemctl start qemu@extract-vbios-nvflash.service. You can also do it over ssh. The extracted ROM will be in the root directory /root/vBIOS.rom
  6. Edit the vBIOS

Method 3 Windows

Get the GPU BIOS Source. You can download the bios from techpowerup.com; if you do so, download a HEX editor and skip to step 5.

  1. Boot the host into Windows.
  2. Download and install GPU-Z.
  3. Download and install a HEX editor.
  4. Open GPU-Z and backup the GPU BIOS. Right next to the Bios Version; in my case 80.04.C3.00.0F, there is an icon for backup. A file named GK104.rom will be created [Your file name may vary].
  5. Edit the vBIOS

Edit the VBIOS

  1. Open the vBIOS ROM (vBIOS.rom) in the HEX editor.
  2. [After a bunch of 00 there is a 55 or U in HEX, delete everything before the 55](/Screenshots/Hex vBIOS.png), and save. I strongly recommend not to overwrite the original ROM.

Configure

  1. Clone this repository
$ git clone https://gitlab.com/YuriAlek/vfio.git
  1. [Optional] Download virtio drivers. If you do not, modify the windows.sh script.
$ wget -o virtio-win.iso "https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso"
  1. Get the iommu groups needed for the VM (GPU, GPU audio and USB controller)
$ chmod +x scripts/iommu.sh
$ scripts/iommu.sh
-------------------------
# GPU
IOMMU group 13
	  06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1)
	  06:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio Controller [10de:0e0a] (rev a1)
# USB 3.0 Controller
IOMMU group 16
	  07:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] USB 3.0 Host controller [1022:145f]
# SATA Controller
IOMMU group 18
	  08:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
  1. [Optional] Create the image for the VM. Only if not using a physical hard drive.
$ qemu-img create -f raw windows.raw 60G

  1. Edit the script windows-install.sh and windows.sh to convenience. Things you may have to edit:

  2. PCI devices

  3. User

  4. Location of HDD, ISO, vBIOS and OVMF image

  5. The Desktop Environment, Display Manager, Window Manager, etc.

  6. QEMU options like RAM and CPU

  7. Kernel modules

  8. Start the VM

# scripts/windows-install.sh

  1. When installing Windows, in the section Where do you want to install Windows? there will be no hard drives to install to; to fix it:

  2. Load driver

  3. Browse

  4. CD Drive (E:) virtio-win-0.1.1

  5. vioscsi

  6. w10

  7. amd64

  8. ok

  9. Load driver Red Hat VirtIO SCSI pass-through controller (E:\vioscsi\w10\amd64\vioscsi.inf)

  10. Next

  11. Select the Unallocated Space

  12. Proceed as normal.

  13. Let Windows find the drivers for the GPU (if Windows has network) or download the updated ones from NVIDIA.

  14. Once installed Windows, run the VM with:

# scripts/windows.sh

For the sake of convenience

# ln -s scripts/qemu@.service /usr/lib/systemd/system/

$ alias windows="sudo systemctl start qemu@windows.service"
$ alias macos="sudo systemctl start qemu@macos-hs.service"

To start the Windows VM

$ windows

To start the MacOS VM

$ macos

For MacOS

Check this amazing guide for creating the MacOS install image and Clover.

Known problems

Race condition

There is something somewhere that makes it crash. That's why there is so many sleep

MacOS does not like USB hubs, therefore anything connected to a hub will be ignored by MacOS

Sometimes works, sometimes does not

Sometimes the GPU will not have correct drivers inside Windows, even when yesterday was working just fine; Windows may install them.

Sometimes the QEMU command will just fail and the command continues and start X again.

Sometimes the QEMU command does not exit after shutting down the VM.

Windows version

Windows 10 Pro 1709 works for me, but 1803 does not (may be the UEFI). I have heard that the 1803 version comes with a Spectre patch and the performance is pathetic.

TODO

  • Unbind GPU without virsh
  • Update macos script
  • Run QEMU as user.
  • Try if is necessary to edit /etc/mkinitcpio.conf. No need to load the kernel modules at boot.
  • Network
  • Audio
  • IOMMU guide
  • Troubleshooting guide
  • Extract the vBIOS in Linux guide
  • How to edit the windows.sh script
  • Fix the race condition
  • Create scripts for install and use (Without DVD images)
  • ACS Patch (Does not work for me).
  • Install guide
  • ???