Andrew Willard Posted March 14, 2018 Share Posted March 14, 2018 Hi everyone i got a asus z87-ws motherboard and 4770k and 32gb of ddr3 + a gigabyte gtx 670. I know the 4770k does not support vt-d passthrough so i went and purchased a 4790k on ebay. Instead of buying a hole new board and ddr4 ram + a new cpu this seemed like the best option for me. When i installed the 4790k and enabled vt-d in the bios. I went right away to my windows 10 vm i had already setup. To enable the gpu passthrough. And noticed it shows a completely different gpu it says gtx 675mx which is a mobile gpu weird. In the drop down menu also it's grouped together in the IOMMU which i know it should be separated. does that mean i need a different board? from what i read online + i can boot into a windows 10 install and download the vbios file for the gtx 670. And add the vbios file and text to the xml of the windows vm. I plan on using gpu-z and downloading the vbios file. Later this afternoon. anyway if anyone has any tips let me know. I would love to get the gpu passthrough working on my rig. Last but not least this is the xml for the windows 10 vm. Were do i put the vbios information in this xml? <domain type='kvm'> <name>Windows 10</name> <uuid>d069e428-2dfb-ed1f-45d2-ca73021503a1</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='4'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/d069e428-2dfb-ed1f-45d2-ca73021503a1_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' check='none'> <topology sockets='1' cores='4' threads='2'/> </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/cache/Operating Systems/Windows 10/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/4TB UNRAID/Windows 10 n stuff/Windows 10 n stuff/Win10_English_x64.iso'/> <target dev='hda' bus='ide'/> <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/4TB UNRAID/virtio-win-0.1.141.iso'/> <target dev='hdb' bus='ide'/> <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='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:93:16:f0'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc315'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0819'/> <product id='0x0101'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x147a'/> <product id='0xe056'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
Squid Posted March 14, 2018 Share Posted March 14, 2018 8 minutes ago, Andrew Willard said: also it's grouped together in the IOMMU which i know it should be separated. Try acs override in VM settings 8 minutes ago, Andrew Willard said: Were do i put the vbios information in this xml? If you upgrade to 6.5.0, there's a spot in the template just for this Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 Ok how do i override acs in vm settings? Also were in the template i don't see it. Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 Ok i found acs override it's in settings vm settings. Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 Ok i got it all running and rebooted and updated to 6.5.0 with acs override. I'll try a couple different vbios files from techpowerup if they don't work i'll boot into a windows 10 install. And grab the vbios file. Thanks for helping me out Squid. I'm sure it will work once i get the right vbios file!!! Cheers!!! Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 So i enabled acs override also figured out which card i have. which is the https://www.gigabyte.com/Graphics-Card/GV-N670WF2-2GD#ov i found the vbios file here https://www.techpowerup.com/vgabios/141821/gigabyte-gtx670-2048-120911 it's a .rom file will that work? I selected the .rom vbios file which is Gigabyte.GTX670.2048.120911.rom i booted the vm and went to install the drivers. And it says this. Also now the gpu shows up as a grid cube? Dunno what to do now. Since i did everything and it won't work. let me know if you can think of any ideas to get it working. Quote Link to comment
Squid Posted March 14, 2018 Share Posted March 14, 2018 Did the VM boot up with the passed through card? I see you were accessing via VNC instead of on the passed through card. Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 When i enable the gpu with the bios file. It starts but no video shows from the monitor connected to the gpu. Also when i try to install the gpu drivers it can't find the graphics card. Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 I'm trying this error 43 workaround out. I did everything installing the drivers now. Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 Well that didn't work reverting back Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 Still have error 43 Quote Link to comment
Andrew Willard Posted March 14, 2018 Author Share Posted March 14, 2018 (edited) Just wanted to post the specs and show that i do have IOMMU enabled. Edited March 14, 2018 by Andrew Willard Quote Link to comment
Siwat2545 Posted March 15, 2018 Share Posted March 15, 2018 Can i have a look at your XML File ? (Paste your xml here) Quote Link to comment
Andrew Willard Posted March 15, 2018 Author Share Posted March 15, 2018 Sure <domain type='kvm'> <name>Windows 10</name> <uuid>d069e428-2dfb-ed1f-45d2-ca73021503a1</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>17301504</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='4'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/d069e428-2dfb-ed1f-45d2-ca73021503a1_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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/cache/Operating Systems/Windows 10/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/4TB UNRAID/Windows 10 n stuff/Windows 10 n stuff/Win10_English_x64.iso'/> <target dev='hda' bus='ide'/> <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/4TB UNRAID/virtio-win-0.1.141.iso'/> <target dev='hdb' bus='ide'/> <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='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:93:16:f0'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/4TB UNRAID/GPU BIOS/Gigabyte.GTX670.2048.120911.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
Andrew Willard Posted March 16, 2018 Author Share Posted March 16, 2018 On 3/15/2018 at 3:56 AM, Siwat2545 said: Can i have a look at your XML File ? (Paste your xml here) I figured out the issue. Bad gpu/Rom I installed windows 10 on the machine. And it gives me the same issues. I'm gonna try the 1080ti from my main rig. If that works on passthrough which it should. I'll get a dedicated gpu for the unraid box. Thanks for putting up with me yall. Quote Link to comment
Taza Posted October 27, 2019 Share Posted October 27, 2019 Hey guys i have also having issues passthru with unraid 6.7.2 and my gigabyte gtx670 OC 2GB With win10 vm. When i start the keyboard flashes a few times it tries to push video thru but then goes back to powersaving mode. I have watched space invaders video but i cant find where to edit the xml file like he does in the video. I dont have the edit xml drop down menu when you click on the windows icon. I have pointed the vbois to a folder where suggested but it doesnt seem to save it when you update I have tried GPU in slot 1 and now currently in slot 2 Also tried the immou overide also and everytime i select no in hyper-v it stays on. System is I9-9900K 32GB 3200MHZ ram Gigabyte GTX 670 OC 10TB parity 480GB crucial ssd for cache 6TB, 4TB, 2TB for array Cheers Taz Quote Link to comment
itimpi Posted October 27, 2019 Share Posted October 27, 2019 In case it helps, if you want to edit the xml then this is now done by selecting the Edit option and then switching the resulting screen to xml mode using the toggle at the top right. Quote Link to comment
Taza Posted October 27, 2019 Share Posted October 27, 2019 Ohhh cheers ill give it a go just wish it just worked lol Taz Quote Link to comment
Taza Posted October 27, 2019 Share Posted October 27, 2019 ive gone through the xml and i cant even see the nvidia in there <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>80a04040-b1be-0f86-1ae0-a0dde00354ea</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='10'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='11'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='12'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/80a04040-b1be-0f86-1ae0-a0dde00354ea_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' check='none'> <topology sockets='1' cores='4' threads='2'/> </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='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows/Win10_1903_V2_English_x64.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/Windows/virtio-win-0.1.160-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 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:28:a8:64'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc248'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x048d'/> <product id='0x8297'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x12cf'/> <product id='0x0219'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='none'/> </devices> </domain> Quote Link to comment
testdasi Posted October 27, 2019 Share Posted October 27, 2019 (edited) 18 minutes ago, Taza said: ive gone through the xml and i cant even see the nvidia in there You need to rewatch SpaceInvaderOne videos, the one about VM basis and progress from there. (If the video you are watching goes straight to xml then you need to find an earlier video). Also, turn off any ad-blocker which may potentially interfere with the GUI. XML mode is a button on the upper right corner when you edit a VM. PS: realised it might have sounded condescending but Unraid learning curve would be incredibly steep if you jump in midway. All the guides and helps have to assume a minimum level of familiarity and your question(s) suggest you are highly unfamiliar. That means you will benefit a lot from starting from the basis and SIO early videos are incredibly good at talking about the basis e.g. the Unraid GUI. Edited October 27, 2019 by testdasi Quote Link to comment
Taza Posted October 27, 2019 Share Posted October 27, 2019 4 minutes ago, testdasi said: You need to rewatch SpaceInvaderOne videos, the one about VM basis and progress from there. (If the video you are watching goes straight to xml then you need to find an earlier video). Also, turn off any ad-blocker which may potentially interfere with the GUI. XML mode is a button on the upper right corner when you edit a VM. Thanks i will give it ago tomorrow and ill turn the ad blocker off on laptop i use to access unraid. Taz Quote Link to comment
Taza Posted November 3, 2019 Share Posted November 3, 2019 tried everything and still nothing think i will buy a new GPU that just work and good enough for decent gaming Cheers Taza Quote Link to comment
ogi Posted March 9, 2020 Share Posted March 9, 2020 I have the same GPU, did a bunch of research; eventually discovered that the passthrough devices need to support UEFI boot, which this Gigabyte card does not support. I'll be trying to flash the vbios linked in that thread to my GPU and see if it works any better. Quote Link to comment
Recommended Posts
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.