GPU passthrough with single GPU


14 posts in this topic Last Reply

Recommended Posts

Hi there,

I am new here and overall in unraid, so I am actually in the trial period and since almost two days I am confronted with a GPU passthrough problem.

 

My system:

Ryzen 9 3900X

64GB (non-ECC) RAM

ASUS TUF Gaming x570 plus Motherboard

Radeon 280X 3GB

512 nvme

and a few old harddisks and ssd´s

 

My goal is to Game almost "nativ" via unraid system. So the final status should be, I am starting the workstation and booting into unraid. Win10 (Virtual Client) starts automatically and I can play games, etc. etc. and also reach my unraid Interface to manage it from the Virtual Client (as far as the VM doesnt need to be restarted =))

 

I ve already installed a full working Windows 10 on my nvme (512GB) and i pass it trough (that works with VNC graphics), but when I try to passthrough my AMD Graphicscard I get some problems :-(

 

My Graphics card (Gpu-Z):

image.png.de29c716c3cc9c3f70beacea4ed309a5.png

 

https://www.techpowerup.com/gpu-specs/xfx-double-d-r9-280x-black-edition.b2671

 

Here are my VM settings:

1.PNG.8f983a3618381812d4d0b99fe4fb6ea4.PNG

 

2.PNG.346602e91c34e22df9b57089e45a1aa0.PNG

 

Logs are showing following errors:

ErrorWarningSystemArrayLogin

2020-08-09T17:57:01.748539Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554a0, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748547Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554a8, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748555Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554b0, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748563Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554b8, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748571Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554c0, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748578Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554c8, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748587Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554d0, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748594Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554d8, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748602Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554e0, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748609Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554e8, 0x0,8) failed: Device or resource busy
2020-08-09T17:57:01.748618Z qemu-system-x86_64: vfio_region_write(0000:08:00.0:region0+0xf3554f0, 0x0,8) failed: Device or resource busy

 

VGA and Graphicsound seems to be in the same IOMMU Group. 

 

Hopefully there is someone who can help me with this issue :'-(

 

Thanks in advance. Kind Regards,

Reini

Link to post
  • 1 month later...

UPDATE:

I figured out a way to pass the GPU through with a GT705... the AMD RX280 caused me problems all over again and never worked.

So i bought an 2060 super from nvidia and now it works without any issues (just enabled ACS) and configured it in the vm settings.

 

But I the next problem is, that I cant figure out a way to get my audio working. I am using a Logitech Z906 Soundsystem and thats connected to the PC via Toslink.

I´ve tried to install "VFIO-PCI Config" Plugin and pass it through but I guess there is something wrong, because the VM will not boot and the whole Unraid is freezing additional I am not sure if I am using the correct device entry.

 

I choosed Group37 to pass through, but it doesnt show up in my VM Setting:

image.png.44b9b3c66961844025e99ae18e1aade2.png

 

IOMMU      ADDRESSBOUNDRESETVENDOR IDDESCRIPTION

Group 0 00:01.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

Group 1 00:01.11022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

Group 2 00:01.21022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

Group 3 00:02.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

Group 4 00:03.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

Group 5 00:03.11022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

Group 6 00:04.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

Group 7 00:05.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

Group 8 00:07.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

Group 9 00:07.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

Group 10 00:08.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

Group 11 00:08.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

Group 12 00:14.01022:790bSMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)

 00:14.31022:790eISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)

Group 13 00:18.01022:1440Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0

 00:18.11022:1441Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1

 00:18.21022:1442Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2

 00:18.31022:1443Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3

 00:18.41022:1444Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4

 00:18.51022:1445Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5

 00:18.61022:1446Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6

 00:18.71022:1447Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7

Group 14 01:00.01987:5012Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01)

Group 15 02:00.01022:57adPCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream

Group 16 03:02.01022:57a3PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

Group 17 03:05.01022:57a3PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

Group 18 03:08.01022:57a4PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

Group 19 03:09.01022:57a4PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

Group 20 03:0a.01022:57a4PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

Group 21 04:00.010de:104cVGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 705] (rev a1)

Group 22 04:00.110de:0e08Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)

Group 23 05:00.010ec:8168Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 26)

Group 24 06:00.01022:1485Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

Group 25 06:00.11022:149cUSB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

USB devices attached to this controller:

Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Group 26 06:00.31022:149cUSB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

USB devices attached to this controller:

Bus 003 Device 002: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Group 27 07:00.01022:7901SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

Group 28 08:00.01022:7901SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

Group 29 09:00.010de:1f06VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] (rev a1)

Group 30 09:00.110de:10f9Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)

Group 31 09:00.210de:1adaUSB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)

USB devices attached to this controller:

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Group 32 09:00.310de:1adbSerial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)

USB devices attached to this controller:

Group 33 0a:00.01022:148aNon-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

Group 34 0b:00.01022:1485Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

Group 35 0b:00.11022:1486Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP

Group 36 0b:00.31022:149cUSB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

USB devices attached to this controller:

Bus 007 Device 003: ID 046d:c088 Logitech, Inc. G Pro Wireless Gaming Mouse

Bus 007 Device 002: ID 258a:1006 Gaming KB Gaming KB

Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Group 37 0b:00.41022:1487Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

 

 

I can select it as a second soundcard, but if I am configuring it like that and startup the VM, the system freezes as i mentioned before:
image.png.260d63ae4209a16ed177f30069b1805f.png

 

Does someone have an idea and may help me? :-( Thanks in advance.

Cheers.

Link to post

There is a bug with amd usb and audio where it won't pass through properly (I've been using my arctis 7 headset in Windows as a workaround for now). Kernel 5.8 was supposed to contain a patch to fix that issue, so you can try 6.9 beta 29 and see if that fixes your issue. I had the same question regarding beta 29 and the audio passthrough fix located here: 

 

Link to post
  • 2 weeks later...

@XS1CHT - sorry for the (maybe) stupid question, but I plan to build my next unraid server very identical 

Ryzen 9 - ASUS TUF Gaming X570 - Asus GeForce RTX 2060 Super ROG Strix OC.

 

I was wondering because I don't read anything that you bought a second GPU. 

But as far as I understood, unRAID @ AMD CPUs (without a IGPU) always need a second GPU to work correctly?

Link to post

I want to add one more thing when using only one gpu.

In my case, with unraid 6.8.3 and a gtx titan black I'm able to start unraid with the gpu output, my vm (macos) is started automatically with that gpu passthrough and a vbios and it switches video correctly, but when I shutdown the vm the gpu doesn't re-attach to unraid, so to shutdown the server I need to short press the power button (or login with ssh from somewhere else); all ok, the server is shutdown properly.

I have also another system with linux manjaro (only cli, no gnome nor kde) running kernels 5.8 (latest stable) and 5.4 lts: in both kernels the gpu is able to attach to linux, to the vm, and back to linux; in other words the gpu attaches to nouveau driver (linux), to vfio (when the vm is started) and back to nouveau.

The problem is that sometimes the gpu hangs with dmar errors in logs and a long press power button is required to shutdown linux.

So, managing gpu passthrough with only one gpu differs from different gpus, you may be lucky or not, I like the way unraid manages this with my gpu, not having any problems with proper shutdown.

Edited by ghost82
Link to post
  • 2 weeks later...

I run into a similar issue, 

However i keep getting the same issue, 

The VNC runs without issues. then when i want to pass anything through there is no reaction.

the monitor remains black, no input. I do see the video card spinning up and the cores being active. 

 

Is this just bad luck with the AMD motherboard? or am I missing something obvious? 

I am currently at the point of rolling back to the "regular" setup. 

 

Tried:

seaBios, OVMF.

Q35 and I440-fx. 

added the suggested rom file. 

Installed the drivers for the 390 directly using the VNC first. 

Added the 127 bug work around. 

 

running on X399 tiachi, with 1950X. 64G ram, and a R9 390 8G MSI video card in the primary slot. 

 

I have the following XML:

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Matthijs</name>
  <uuid>9049d992-f9ca-da4a-26b4-f87220adab1b</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>20</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='18'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='19'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='20'/>
    <vcpupin vcpu='6' cpuset='5'/>
    <vcpupin vcpu='7' cpuset='21'/>
    <vcpupin vcpu='8' cpuset='6'/>
    <vcpupin vcpu='9' cpuset='22'/>
    <vcpupin vcpu='10' cpuset='7'/>
    <vcpupin vcpu='11' cpuset='23'/>
    <vcpupin vcpu='12' cpuset='8'/>
    <vcpupin vcpu='13' cpuset='24'/>
    <vcpupin vcpu='14' cpuset='9'/>
    <vcpupin vcpu='15' cpuset='25'/>
    <vcpupin vcpu='16' cpuset='10'/>
    <vcpupin vcpu='17' cpuset='26'/>
    <vcpupin vcpu='18' cpuset='11'/>
    <vcpupin vcpu='19' cpuset='27'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='10' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Matthijs/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x14'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </controller>
    <controller type='pci' index='7' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:f1:5d:78'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/domains/vbios/MSIR9390X.rom'/>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x43' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x02' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc534'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>
 

 

 

Link to post
  • 4 weeks later...

@mikotoiii thx for your reply and sorry for my late reply, yes I solved it with a newer version of unraid (at the moment I am on beta 35, but it worked already with version 30) thank you! But to be honest, I am not sure if I will stay with Unraid, my system freezes every day 3-4 times, I think it´s an Issue with the soundsystem (connected as mentioned via TOSLINK) or maybe its according to Spotify - I´ve no idea... 

Interessing fact, If I switch the audio Input to my headset (connected to the fron panel AUX conection) and starting CS GO (Counter Strike) for a game and playing a song in spotify, there´s no Issue, so I guess its something wrong with the connected Logitech Soundsystem to the TOSLINK 😞 

On and on it helps to Pause the VM and Resume it again, but not always.

 

Btw. another Issue - I had sooo many USB Problems caused by the following Passthrough:

image.png.f3317c3cfd23c0709e88e9eb3fad143d.png

Since I´ve disbaled the "ASUSTek Computer AURA LED Controller" I´ve less Issues... just 4 info, if someone using a ASUS TUF Gaming x570 PLUS as I do...

Link to post

I successfully passed through 1 gpu by following SpaceInvader One's youtube video on gpu passthrough editing the dumped rom from my gpu.

 

I also added my onboard audio to vfio-pci.ids.

 

When adding it to the VM i passed through the gpu and gpu audio, added onboard audio as second audio device, then added a startup script to unbind the gpu from unraid in user scripts plugin.

 

#!/bin/bash
echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind

 

That's what worked for me, your experience of this may differ. I have a gigabyte b450 aorus itx, r5 2600, GTX 1050ti.

 

 

Link to post
On 10/12/2020 at 2:11 PM, ghost82 said:

The problem is that sometimes the gpu hangs with dmar errors in logs and a long press power button is required to shutdown linux.

So, managing gpu passthrough with only one gpu differs from different gpus, you may be lucky or not, I like the way unraid manages this with my gpu, not having any problems with proper shutdown.

I was wrong..in manjaro dmar errors were fixed with kernel updates and the hang was due to bugged wifi driver for my usb wifi dongle, blacklisting it (I don't need wifi on the host) finally solved the issue of "hang on shutdown".

So it would be good if also unraid was able to switch from opensource to vfio and the other hand so to be able to manage all with a single gpu.

At least in my case it will work, but maybe this would be a pain in other cases.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.