Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Win10 VM - Only some Remote options work

Featured Replies

For the past few weekends I've been working on getting a VM working with my Gigabyte Nvidia GeForce GTX 1060 card with Passthrough.  I eventually got windows to see it fine (without the Windows Code 43 error) by disabling Windows 10 Auto driver installation.  So it appears to work fine, I'm able to use Steam Stream to play games.  I am able to RDP flawlessly.  The problem I am running into is I cant get Moonlight to work.  It just displays a black screen.  In further testing I was never able to get Splashtop Personal to work.  At best I will be able to Login to Win10 then its screen goes black with Splashtop.  Anydesk, wont connect just sits there saying "Connected, waiting for image".  TeamViewer will sort of work, have to keep selecting "Refresh Image" sometimes. 

 

I was able to I think dump my video cards vbios, for some reason it is only 58KB, the VM seems to work fine with it, it will also work with a modified one from TechPowerUP at 242KB.

 

I have unraid set to use the GUI from the onboard/onchip video, other than that I just have this Nvidia 1060 in the system.
Has anyone run into this before?  There is clearly an issue where some work some don't.  I've tried another new install of Win10.  I'm using the latest 1809 version of windows 10.  Unraid is on version 6.6.6.  Any Ideas, I'm a little weirded out by some things working and some not and I've read Moonlight works better than steam stream.  Let me know if you need any more info I have not already given.  Thanks

 

Screenshot_99.png

To be honest, the auto-driver install should work fine, and the fact that it doesn't and that moonlight also has issues shows that you probably don't have a complete passthrough yet...  It is normal for the card to work just fine on first boot, but if the passthrough is not working correctly than a reboot of the VM wont be able to correctly reset the PCIe slot for the card, and so it will still be stuck trying to talk to the now rebooted VM...

 

The ROM files that I download from my card manufacturer are also around 251k, but the one I dumped from my GTX1070 is around 126K, and the ones download from the Manufacturer even when they are the ones currently applied to the card using the normal Windows (Baremetal) don't work...  There are other places to get the ROM, but the ones from the card directly are best... Yours being a GTX1060 might be smaller than mine, but I would not expect it to be 50% the size...

 

We would need the VM's XML file, and the diagnostics file to be able to help further...

  • Author

Appreciate the reply, yea, I have been wondering the same thing.  It may seem fine in windows but not completely...I'll see if I can dump it again, last ditch, install the 1060 into another windows computer and try to pull the bios from GPU-Z.  Bellow is my XML, IOMMU, and Logs from the VM.  If that isn't the diagnostics please forgive my stupidity and let me know exactly what you are looking for there.

 

Quote

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='22'>
  <name>Windows 10</name>
  <uuid>7e2b19db-c583-cf31-b1b7-0b5382436de7</uuid>
  <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'>6</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='2'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='3'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
 <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/7e2b19db-c583-cf31-b1b7-0b5382436de7_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='3' 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/user/domains/Windows 10/vdisk1.img'/>
      <backingStore/>
<target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <alias name='virtio-disk2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/Games/vdisk2.img'/>
      <backingStore/>
      <target dev='hdd' bus='virtio'/>
      <alias name='virtio-disk3'/>
      <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.iso'/>
      <backingStore/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <alias name='ide0-0-0'/>
      <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.160-1.iso'/>
      <backingStore/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <alias name='ide0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <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'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
 <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:8d:6c:b9'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
 <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-22-Windows 10/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='3'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
 <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <rom file='/mnt/user/poste/GPU BIOS/1060.rom'/>
      <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='0x00' slot='0x03' function='0x0'/>
      </source>
      <alias name='hostdev1'/>
      <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='0xc016'/>
        <address bus='3' device='2'/>
      </source>
      <alias name='hostdev2'/>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
<source>
        <vendor id='0x413c'/>
        <product id='0x2105'/>
        <address bus='3' device='4'/>
      </source>
      <alias name='hostdev3'/>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

Quote

2019-02-24T22:17:47.530117Z qemu-system-x86_64: terminating on signal 15 from pid 5328 (/usr/sbin/libvirtd)
2019-02-24 22:17:48.952+0000: shutting down, reason=shutdown
2019-02-24 22:43:25.151+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Media
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-20-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/7e2b19db-c583-cf31-b1b7-0b5382436de7_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 7e2b19db-c583-cf31-b1b7-0b5382436de7 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=27,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,master29,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8d:6c:b9,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=32,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=3 -device 'vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/mnt/user/poste/GPU BIOS/TPUGigabyte.GTX1060.6144.160728.rom' -device vfio-pci,host=00:03.0,id=hostdev1,bus=pci.0,addr=0x8 -device usb-host,hostbus=3,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=3,hostaddr=4,id=hostdev3,bus=usb.0,port=2 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
2019-02-24 22:43:25.151+0000: Domain id=20 is tainted: high-privileges
2019-02-24 22:43:25.151+0000: Domain id=20 is tainted: host-cpu
2019-02-24T22:43:25.200206Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2019-02-24T22:43:40.276030Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.
2019-02-24T22:43:40.387020Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.
2019-02-26T04:25:44.657949Z qemu-system-x86_64: terminating on signal 15 from pid 5328 (/usr/sbin/libvirtd)
2019-02-26 04:25:45.684+0000: shutting down, reason=shutdown
2019-02-26 04:27:31.135+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Media
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-21-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/7e2b19db-c583-cf31-b1b7-0b5382436de7_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 6144 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 7e2b19db-c583-cf31-b1b7-0b5382436de7 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=27,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,master29,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8d:6c:b9,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=31,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=3 -device 'vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/mnt/user/poste/GPU BIOS/TPUGigabyte.GTX1060.6144.160728.rom' -device vfio-pci,host=00:03.0,id=hostdev1,bus=pci.0,addr=0x8 -device usb-host,hostbus=3,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=3,hostaddr=4,id=hostdev3,bus=usb.0,port=2 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
2019-02-26 04:27:31.135+0000: Domain id=21 is tainted: high-privileges
2019-02-26 04:27:31.135+0000: Domain id=21 is tainted: host-cpu
2019-02-26T04:27:31.177953Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2019-02-26T04:27:32.365084Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.
2019-02-26T04:27:32.475105Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.
2019-03-01T18:38:20.023920Z qemu-system-x86_64: terminating on signal 15 from pid 5328 (/usr/sbin/libvirtd)
2019-03-01 18:38:20.454+0000: shutting down, reason=shutdown
2019-03-01 18:39:45.476+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Media
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-22-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/7e2b19db-c583-cf31-b1b7-0b5382436de7_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 6144 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 7e2b19db-c583-cf31-b1b7-0b5382436de7 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=27,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,master29,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8d:6c:b9,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=31,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=3 -device 'vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/mnt/user/poste/GPU BIOS/1060.rom' -device vfio-pci,host=00:03.0,id=hostdev1,bus=pci.0,addr=0x8 -device usb-host,hostbus=3,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=3,hostaddr=4,id=hostdev3,bus=usb.0,port=2 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
2019-03-01 18:39:45.476+0000: Domain id=22 is tainted: high-privileges
2019-03-01 18:39:45.476+0000: Domain id=22 is tainted: host-cpu
2019-03-01T18:39:45.517737Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2019-03-01T18:39:46.375082Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.
2019-03-01T18:39:46.483062Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.

 

Quote

IOMMU group 0:    [8086:0c00] 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
IOMMU group 1:    [8086:0c01] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
IOMMU group 2:    [8086:0412] 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
IOMMU group 3:    [8086:0c0c] 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
IOMMU group 4:    [8086:8cb1] 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
IOMMU group 5:    [8086:8cba] 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
IOMMU group 6:    [8086:15a1] 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V
IOMMU group 7:    [8086:8cad] 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
IOMMU group 8:    [8086:8ca0] 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
IOMMU group 9:    [8086:8c90] 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
IOMMU group 10:    [8086:244e] 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d0)
IOMMU group 11:    [8086:8c98] 00:1c.4 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 (rev d0)
IOMMU group 12:    [8086:8ca6] 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
IOMMU group 13:    [8086:8cc4] 00:1f.0 ISA bridge: Intel Corporation Z97 Chipset LPC Controller
    [8086:8c82] 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
    [8086:8ca2] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
IOMMU group 14:    [10de:1c03] 01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
IOMMU group 15:    [10de:10f1] 01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
IOMMU group 16:    [1b21:1080] 03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04)
IOMMU group 17:    [1b21:1242] 05:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller

 

Diagnostics is under the "Tools" menu, then under diagnostics, then just click "Download"...  Also just for the future, the "Code" button is the one you want to click when posting XML code, the "Quote" button makes everything hard to read...  Or better yet, paste it into a text file and just drag the file into this window...  Not chewing you out, just mentioning for the future...

 

Edit: Also, reading through what you did have posted:

Quote

.......

2019-03-01T18:39:46.375082Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.
2019-03-01T18:39:46.483062Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.0, depends on group 15 which is not owned.

.......

This looks like that reset of the GPU thing that I was talking about, so it looks like it is not fully passed through yet...

Edited by Warrentheo

  • Author

Thanks for the tip, I almost used Code, but switched to Quote.  Diagnostics are attached if still needed, but I think your right.  I need to get the vbios right.  I may not get to that till next Friday, but will definitely report back here with my results.  Thanks for your help.

media-diagnostics-20190301-2021.zip

@Phase1 I had that issue by forgetting to passthrough the audio portion of the card. Only happens if it sits on the top PCIe slot. The same card on one of the other slots works for me without the audio passthrough. 

 

Edit:

Another thing to mention, if you select the cores for the VM, always use the core and it's HT and skip the core 0 and it's HT core. It's used by Unraid itself. Remove core 4 and use core 7 instead.

Edited by bastl

  • Author

Thanks for the reply @bastl.  I did try moving the card to another slot, so far no luck.  I even removed the card and put it in another desktop and was able to export the bios from the card using GPU-Z.  Its actually 245KB.  So I think its pretty clear with @Warrentheo advice that I did not have correct vbios.  I've tried booting the VM with the new bios file, and even tried trimming the file as mentioned in one of SpaceInvader's videos.  Neither appear to be working.  The Code 43 is back in windows.  And still getting these issues in the VM Log

 

Quote

2019-03-02T20:48:11.803533Z qemu-system-x86_64: vfio: Cannot reset device 0000:02:00.0, depends on group 16 which is not owned.

Typically should I need to trim the bios file with a hex editor if its pulled directly from the card?  Any other ideas?  I appreciate your feedback so far.  I also fixed the CPU/Core thing too you mentioned. 

  • Author

Made some progress but still have exact same issue.  Got rid of the previous error:  vfio: Cannot reset device 0000:02:00.0, depends on group 16 which is not owned. by selecting the nvidia audio controller for the sound card (seems obvious now I might have to add that).  Previously I never even selected a sound card.  That's what group 16 was referenced too.

 

 

IOMMU group 16:    [10de:10f1] 02:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)

 

And after nvidia driver uninstalls re-installs etc, with the hex edited bios file from the GPU added I no longer have the Code 43 error.  But still have the exact same problems as I started with. 

 

  • 3 weeks later...
  • Author

Finally solved it, turns out with the nvidia gtx 1060 you need the video card attached to a monitor or a dummy monitor plug for windows to like it.  Maybe you need it for all GPU's this is just new to me.  I follow the /r/homelab subreddit and saw someone trying to get a headless Win10 working using VMWare and someone responded with its working fine with their 1060 with a HDMI dongle.  I have a crappy monitor next to my unraid box for emergencies, and I attached it and everything seems to work like it should now.  I hate easy stuff but glad I figured it out.  Only minor problem is with moonlight the resolution requirements for the game are the max for the monitor attached.  I've ordered a DVI dummy plug last night.  Very much appreciate your help and insight.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.