I need help passing through GTX 960 to Windows 10 VM

Koitosake · September 5, 2017

I've watched all of @gridrunner videos on youtube, sometimes religiously. But I'm still running in to problems. I'm working on unRAID machine for work and I've been able to create a couple VM's in SeaBIOS and OVMF, but I cannot connect to them other than with VNC.

My hardware is:
Mobo: TYAN - S5396
CPUs Dual Xeon 3.0ghz

GFX GeForce GTX 760 ( I do have other options and cards I can use)

16gb ECC RAM PC2-5300f

The only issue I KNOW I have with my hardware is that it beeps at me if I have a gfx card in the first PCIe slot when I try to boot it. But it seems just fine in the other PCIe slot until I turn on the VM.

Now I did run in to issues getting the IOMMU enabled on my mobo at the beginning of my adventure at work here, but I updated the BIOS and turning on the intel vt-d didnt disable the nic's on my board anymore haha.

So now the issue is just passing through the GFX card, so that I can use the VM's to their full potential.

Before turning on PCIe ACS Override here are my IOMMU groups

Quote


IOMMU group 0
	[8086:4001] 00:00.0 Host bridge: Intel Corporation 5400 Chipset Memory Controller Hub (rev 20)
IOMMU group 1
	[8086:4021] 00:01.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 1 (rev 20)
	[10de:1187] 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
	[10de:0e0a] 01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
IOMMU group 2
	[8086:4025] 00:05.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 5 (rev 20)
IOMMU group 3
	[8086:4029] 00:09.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 9 (rev 20)
	[8086:3500] 09:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
	[8086:350c] 09:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
	[8086:3510] 0a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
	[8086:3518] 0a:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01)
	[1b4b:9230] 0b:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)
	[8086:1096] 0f:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
	[8086:1096] 0f:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
IOMMU group 4
	[8086:4030] 00:10.0 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.1 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.2 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.3 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.4 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
IOMMU group 5
	[8086:4031] 00:11.0 Host bridge: Intel Corporation 5400 Chipset CE/SF Registers (rev 20)
IOMMU group 6
	[8086:4035] 00:15.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
	[8086:4035] 00:15.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
IOMMU group 7
	[8086:4036] 00:16.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
	[8086:4036] 00:16.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
IOMMU group 8
	[8086:269a] 00:1b.0 Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller (rev 09)
IOMMU group 9
	[8086:2690] 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
IOMMU group 10
	[8086:2688] 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
	[8086:2689] 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
	[8086:268a] 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
	[8086:268b] 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)
	[8086:268c] 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
IOMMU group 11
	[8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
	[104c:8023] 20:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
IOMMU group 12
	[8086:2670] 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
	[8086:269e] 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
	[8086:2680] 00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
	[8086:269b] 00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)

After they are

Quote


IOMMU group 0
	[8086:4001] 00:00.0 Host bridge: Intel Corporation 5400 Chipset Memory Controller Hub (rev 20)
IOMMU group 1
	[8086:4021] 00:01.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 1 (rev 20)
IOMMU group 2
	[8086:4025] 00:05.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 5 (rev 20)
IOMMU group 3
	[8086:4029] 00:09.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 9 (rev 20)
IOMMU group 4
	[8086:4030] 00:10.0 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.1 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.2 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.3 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
	[8086:4030] 00:10.4 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
IOMMU group 5
	[8086:4031] 00:11.0 Host bridge: Intel Corporation 5400 Chipset CE/SF Registers (rev 20)
IOMMU group 6
	[8086:4035] 00:15.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
	[8086:4035] 00:15.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
IOMMU group 7
	[8086:4036] 00:16.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
	[8086:4036] 00:16.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
IOMMU group 8
	[8086:269a] 00:1b.0 Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller (rev 09)
IOMMU group 9
	[8086:2690] 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
IOMMU group 10
	[8086:2688] 00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
	[8086:2689] 00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
	[8086:268a] 00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
	[8086:268b] 00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)
	[8086:268c] 00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
IOMMU group 11
	[8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
	[104c:8023] 20:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
IOMMU group 12
	[8086:2670] 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
	[8086:269e] 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
	[8086:2680] 00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
	[8086:269b] 00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
IOMMU group 13
	[10de:1187] 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
	[10de:0e0a] 01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
IOMMU group 14
	[8086:3500] 09:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
	[8086:350c] 09:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
	[8086:3510] 0a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
	[8086:3518] 0a:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01)
	[1b4b:9230] 0b:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)
	[8086:1096] 0f:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
	[8086:1096] 0f:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)

And here is one of the VMs XML

Quote

<domain type='kvm'>
<name>Windows 10</name>
<uuid>3fa22729-1c22-abcd-4699-e7d25e5af61d</uuid>
<description>Test 2</description>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>6291456</memory>
<currentMemory unit='KiB'>6291456</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>4</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='0'/>
<vcpupin vcpu='1' cpuset='1'/>
<vcpupin vcpu='2' cpuset='2'/>
<vcpupin vcpu='3' cpuset='3'/>
</cputune>
<os>
<type arch='x86_64' machine='pc-q35-2.7'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/3fa22729-1c22-abcd-4699-e7d25e5af61d_VARS-pure-efi.fd</nvram>
</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'>
<topology sockets='1' cores='4' threads='1'/>
</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/Windows 10/vdisk1.img'/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/Windows 10.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.126-2.iso'/>
<target dev='hdb' bus='sata'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<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>
<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='dmi-to-pci-bridge'>
<model name='i82801b11-bridge'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
</controller>
<controller type='pci' index='2' model='pci-bridge'>
<model name='pci-bridge'/>
<target chassisNr='2'/>
<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='0x02' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:bf:02:68'/>
<source bridge='virbr0'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</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='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</source>
<address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/>
</source>
<rom file='/mnt/user/OIS/Daniel/3/760.rom'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc077'/>
</source>
<address type='usb' bus='0' port='1'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x413c'/>
<product id='0x2005'/>
</source>
<address type='usb' bus='0' port='2'/>
</hostdev>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>
</memballoon>
</devices>
</domain>

I've been playing with this server for 2 weeks on and off, and its frustrating that I can get a VM created and up and running, but I cant seem to get the video pass through to work.

2.6k · September 5, 2017

Tools>diagnostics

post that that zip file.

Koitosake · September 5, 2017

Here we go!

cerebra-diagnostics-20170905-1345.zip

Tyranian · September 5, 2017

Check your card has a uefi supported bios on the 760's not all did that could the cause of your issue.

https://www.techpowerup.com/vgabios/ <---- check here

Edited September 5, 2017 by Tyranian

2.6k · September 5, 2017

Diagnostics are from after a reboot and don't list the kvm error. Please try to start the vm, then copy/paste the vm error and/or describe what exactly is happening.

Additionally, if this board doesn't have onboard graphics, you either need to 1. find the video from @gridrunner that explains how to get around this or 2. put in a cheap/old gpu for unRaid to use, freeing up the other one for passthrough.

Koitosake · September 5, 2017

Its a server board so no onboard video. I cant seem to get the system to boot with anything in the top PCIe slot, so I dont know if the cheap/old card will work on this current board.

I'll try to run a few of the VM's and repost the diag. There isnt an error that I can see, the vm starts and the screen just stays black.

Edited September 5, 2017 by Koitosake

Koitosake · September 5, 2017

Here is a hopefully more full of details diagnostic zip, I made a new vm with OVMF, and launched it, and got nothing, and then tried launching one that i had the bios for the video card in the xml.
I'll keep messing with some settings and whatnot and maybe upload another diagnostic file if it'll help. I'm just not sure where I'm getting stuck.

cerebra-diagnostics-20170905-1625.zip

2.6k · September 6, 2017

your libvert error messages:

2017-09-05 21:28:04.343+0000: 4728: error : qemuMonitorIORead:586 : Unable to read from monitor: Connection reset by peer
2017-09-05 21:28:04.344+0000: 4728: error : qemuProcessReportLogError:1809 : internal error: qemu unexpectedly closed the monitor: 2017-09-05T21:28:04.312717Z qemu-system-x86_64: -device usb-host,hostbus=3,hostaddr=52,id=hostdev1,bus=usb.0,port=1: failed to find host usb device 3:52

also this (but may not actually be a problem)

2017-09-05 21:28:43.887+0000: 4730: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2017-09-05 21:28:43.887+0000: 4730: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id

from your syslog:

Sep  5 12:47:51 Cerebra kernel: usb 3-1: USB disconnect, device number 81
Sep  5 12:47:53 Cerebra kernel: usb 3-1: new low-speed USB device number 82 using uhci_hcd
Sep  5 12:47:53 Cerebra kernel: input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/0003:046D:C077.0052/input/input87
Sep  5 12:47:53 Cerebra kernel: hid-generic 0003:046D:C077.0052: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.1-1/input0
Sep  5 12:48:54 Cerebra kernel: usb 3-1: USB disconnect, device number 82
Sep  5 12:48:55 Cerebra kernel: usb 3-1: new low-speed USB device number 83 using uhci_hcd
Sep  5 12:48:55 Cerebra kernel: input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/0003:046D:C077.0053/input/input88
Sep  5 12:48:55 Cerebra kernel: hid-generic 0003:046D:C077.0053: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.1-1/input0

Maybe your mouse is going to sleep? occurs nearly a hundred times, every minute or so.

and lots of usb resets

ep  5 15:48:55 Cerebra kernel: usb 3-1: reset low-speed USB device number 54 using uhci_hcd
Sep  5 15:48:56 Cerebra kernel: usb 2-1: reset low-speed USB device number 3 using uhci_hcd
Sep  5 15:48:59 Cerebra kernel: usb 3-1: reset low-speed USB device number 54 using uhci_hcd
Sep  5 15:49:00 Cerebra kernel: usb 2-1: reset low-speed USB device number 3 using uhci_hcd
Sep  5 15:49:00 Cerebra kernel: usb 3-1: reset low-speed USB device number 54 using uhci_hcd
Sep  5 15:49:01 Cerebra kernel: usb 2-1: reset low-speed USB device number 3 using uhci_hcd
Sep  5 15:49:02 Cerebra kernel: usb 3-1: reset low-speed USB device number 54 using uhci_hcd
Sep  5 15:49:03 Cerebra kernel: usb 2-1: reset low-speed USB device number 3 using uhci_hcd
Sep  5 15:49:08 Cerebra kernel: usb 3-1: reset low-speed USB device number 54 using uhci_hcd
Sep  5 15:49:08 Cerebra kernel: usb 2-1: reset low-speed USB device number 3 using uhci_hcd
Sep  5 15:49:09 Cerebra kernel: usb 3-1: reset low-speed USB device number 54 using uhci_hcd
Sep  5 15:49:09 Cerebra kernel: usb 2-1: reset low-speed USB device number 3 using uhci_hcd
Sep  5 15:49:10 Cerebra kernel: usb 3-1: reset low-speed USB device number 54 using uhci_hcd

maybe normal? I don't know, I dont have this type of activity on my system.

This pertains to your GPU

Sep  5 16:24:51 Cerebra kernel: vfio-pci 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
Sep  5 16:24:51 Cerebra kernel: vfio-pci 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

Never seen that one either.

Don't use ovmf for now, stick with seabios.

4 hours ago, Koitosake said:

Its a server board so no onboard video. I cant seem to get the system to boot with anything in the top PCIe slot, so I dont know if the cheap/old card will work on this current board.

check your bios and see if there is a configuration for primary video in slot 1(or whatever the top slot is) and specify that.

Otherwise, time for you to google a bit and see what pops up

SpaceInvaderOne · September 6, 2017

@Koitosake looking in your qemu log file I see

vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device 
vfio-pci,host=01:00.1,id=hostdev1,bus=pci.0,addr=0x6,romfile=/mnt/user/OIS/Daniel/3/760.rom -device

You have attached your ROM file to the wrong device. the 01:00.1 is the sound part of the GPU. The ROM file must be pointed to the graphics only part (01:00.0)

here is what your XML should look like

  <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/OIS/Daniel/3/760.rom'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
    </hostdev>

Also, make sure that you have removed the header from the ROM file to make it KVM compatible if you have downloaded this from techpowerup

Also if you are passing through a ROM file use ovmf . Seabios probably won't work when passing a ROM file .

Edited September 6, 2017 by gridrunner

Koitosake · September 6, 2017

@gridrunner Thanks so much. I'm a little star stuck, I love your vids.

I had read that the ROM passtrhough was only for OVMF, I was just frustrated I'd felt like I'd tried everything ha.

New in to the IT field and I'm loving playing with unRAID at home and at work, and this was giving me so much issue, and it was right in front of my face!

Ran in to some issues getting these VM's I had already installed to play nice, so now I'm making a fresh one.

Thanks again!

SpaceInvaderOne · September 7, 2017

19 hours ago, Koitosake said:

@gridrunner Thanks so much. I'm a little star stuck, I love your vids.

I had read that the ROM passtrhough was only for OVMF, I was just frustrated I'd felt like I'd tried everything ha.

New in to the IT field and I'm loving playing with unRAID at home and at work, and this was giving me so much issue, and it was right in front of my face!

Ran in to some issues getting these VM's I had already installed to play nice, so now I'm making a fresh one.

Thanks again!

lol, your welcome @Koitosake glad you got it going. Yeah unRAID is definitely a lot of fun

alturismo · September 18, 2017

On 6.9.2017 at 9:57 AM, gridrunner said:

@Koitosake looking in your qemu log file I see

You have attached your ROM file to the wrong device. the 01:00.1 is the sound part of the GPU. The ROM file must be pointed to the graphics only part (01:00.0)

here is what your XML should look like

Also, make sure that you have removed the header from the ROM file to make it KVM compatible if you have downloaded this from techpowerup

Also if you are passing through a ROM file use ovmf . Seabios probably won't work when passing a ROM file .

Hi, may i ask howto remove the header u mentioned here, i would like to test with rom file cause under some circumstances my Nvidia VM is not bootable anymore until a full unraid reboot, may this helps ...

so i found a rom file from teckpowerup, but cant find anything about removing header from rom file ...

for an tip, thanks ahead.

saarg · September 18, 2017

4 hours ago, alturismo said:

Hi, may i ask howto remove the header u mentioned here, i would like to test with rom file cause under some circumstances my Nvidia VM is not bootable anymore until a full unraid reboot, may this helps ...

so i found a rom file from teckpowerup, but cant find anything about removing header from rom file ...

for an tip, thanks ahead.

@gridrunner has made a guide for removing the header, so check his YouTube channel.

SpaceInvaderOne · September 18, 2017

4 hours ago, alturismo said:

Hi, may i ask howto remove the header u mentioned here, i would like to test with rom file cause under some circumstances my Nvidia VM is not bootable anymore until a full unraid reboot, may this helps ...

so i found a rom file from teckpowerup, but cant find anything about removing header from rom file ...

for an tip, thanks ahead.

3 minutes ago, saarg said:

@gridrunner has made a guide for removing the header, so check his YouTube channel.

Hi Yes, here is the video how to

alturismo · September 18, 2017

7 hours ago, gridrunner said:

Hi Yes, here is the video how to

7 hours ago, saarg said:

@gridrunner has made a guide for removing the header, so check his YouTube channel.

thanks alot, thats nice and easy, i ll give it a try and see if that helps

I need help passing through GTX 960 to Windows 10 VM

Recommended Posts

Koitosake

Link to comment

1812

Link to comment

Koitosake

Link to comment

Tyranian

Link to comment

1812

Link to comment

Koitosake

Link to comment

Koitosake

Link to comment

1812

Link to comment

SpaceInvaderOne

Link to comment

Koitosake

Link to comment

SpaceInvaderOne

Link to comment

alturismo

Link to comment

saarg

Link to comment

SpaceInvaderOne

Link to comment

alturismo

Link to comment

Join the conversation