Code 10 Graphics Error on Windows 10

[stratigary]

So, a little bit ago I posted that I had issues getting my GTX 550Ti to work after a reboot and, after searching, found that the card just wasn't going to work on a VM.  The thread is here: http://lime-technology.com/forum/index.php?topic=46582.0

 

To solve this I got a simple replacement, a GeForce gt 610 and created an entirely new VM to start from scratch.  Now I have a new issue.  When I first installed it, everything worked fine as the drivers installed and both monitors worked.  When the VM restarted a day or two later (after updates) it detects the card in the device manager but give a Code 10 saying:

 

"This device cannot start" "This device does not exist"

 

I tried restarting again, but it just doesn't work.  Any help would be greatly appreciated.

 

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:16.1 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #2 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d5)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C224 Series Chipset Family Server Standard SKU LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
04:01.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)
05:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
08:00.0 USB controller: Fresco Logic Device 1100 (rev 10)
09:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 02)
0a:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 21)

 

/sys/kernel/iommu_groups/0/devices/0000:00:00.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.0
/sys/kernel/iommu_groups/2/devices/0000:00:01.1
/sys/kernel/iommu_groups/3/devices/0000:00:14.0
/sys/kernel/iommu_groups/4/devices/0000:00:16.0
/sys/kernel/iommu_groups/4/devices/0000:00:16.1
/sys/kernel/iommu_groups/5/devices/0000:00:1a.0
/sys/kernel/iommu_groups/6/devices/0000:00:1c.0
/sys/kernel/iommu_groups/7/devices/0000:00:1c.1
/sys/kernel/iommu_groups/8/devices/0000:00:1c.4
/sys/kernel/iommu_groups/9/devices/0000:00:1c.5
/sys/kernel/iommu_groups/10/devices/0000:00:1c.6
/sys/kernel/iommu_groups/11/devices/0000:00:1c.7
/sys/kernel/iommu_groups/12/devices/0000:00:1d.0
/sys/kernel/iommu_groups/13/devices/0000:00:1f.0
/sys/kernel/iommu_groups/13/devices/0000:00:1f.2
/sys/kernel/iommu_groups/13/devices/0000:00:1f.3
/sys/kernel/iommu_groups/14/devices/0000:01:00.0
/sys/kernel/iommu_groups/14/devices/0000:01:00.1
/sys/kernel/iommu_groups/15/devices/0000:03:00.0
/sys/kernel/iommu_groups/15/devices/0000:04:01.0
/sys/kernel/iommu_groups/16/devices/0000:05:00.0
/sys/kernel/iommu_groups/17/devices/0000:06:00.0
/sys/kernel/iommu_groups/18/devices/0000:07:00.0
/sys/kernel/iommu_groups/19/devices/0000:08:00.0
/sys/kernel/iommu_groups/20/devices/0000:09:00.0
/sys/kernel/iommu_groups/20/devices/0000:0a:00.0

[tayshun12]

Try removing it from the graphics card option and put vnc back as default.

 

Then manually edit XML like this (you should copy/paste your original into notepad for safe keeping):

 

underneath <qemu:commandline> add:

 

   <qemu:arg value='-device'/>
    <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/>

 

and Remove the following lines

 

   <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
<video>
<model type=’vmvga’ vram=’16384? heads=’1’/>
<address type=’pci’ domain=’0x0000? bus=’0x00? slot=’0x01? function=’0x0’/>
</video>

 

and see if it works

[stratigary]

Thanks!  I'll give this a shot when I get off of work and report back.

[tayshun12]

Hoping all the best!

 

T

[stratigary]

I'm not seeing <qemu:commandline> in my xml file.  Am I doing missing something?

 

<domain type='kvm'>
  <name>Windows 10 - Steve</name>
  <uuid>73d23d52-1257-6fe8-90ed-96fb0dba9937</uuid>
  <metadata>
    <vmtemplate name="Custom" icon="windows.png" os="windows"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='5'/>
    <vcpupin vcpu='2' cpuset='6'/>
    <vcpupin vcpu='3' cpuset='7'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='4' threads='1'/>
  </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/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/cache/vdisks/Windows 10 - Steve/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.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/ISOs/virtio-win-0.1.102.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 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='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:29:82:f6'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 10 - Steve.org.qemu.guest_agent.0'/>
      <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'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='vmvga' vram='16384' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc52b'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc30a'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x1f44'/>
        <product id='0x0050'/>
      </source>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
</domain>

[tayshun12]

Add it under </devices> like so:

 

  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/>
  </qemu:commandline>
</domain>

 

 

[stratigary]

Sorry, that didn't seem to work.  I added and removed what you mentioned, but got this error when trying to start the VM

internal error: early end of file from monitor: possible problem:
2016-03-03T10:13:34.630520Z qemu-system-x86_64: -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1: vfio: Error: Failed to setup INTx fd: Device or resource busy
2016-03-03T10:13:34.630689Z qemu-system-x86_64: -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1: Device initialization failed
2016-03-03T10:13:34.630699Z qemu-system-x86_64: -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1: Device 'vfio-pci' could not be initialized

 

here is the xml file I am using

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Windows 10 - Steve</name>
  <uuid>73d23d52-1257-6fe8-90ed-96fb0dba9937</uuid>
  <metadata>
    <vmtemplate name="Custom" icon="windows.png" os="windows"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='5'/>
    <vcpupin vcpu='2' cpuset='6'/>
    <vcpupin vcpu='3' cpuset='7'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='4' threads='1'/>
  </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/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/cache/vdisks/Windows 10 - Steve/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.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/ISOs/virtio-win-0.1.102.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 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='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:29:82:f6'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 10 - Steve.org.qemu.guest_agent.0'/>
      <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'/>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc52b'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc30a'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x1f44'/>
        <product id='0x0050'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x04' slot='0x01' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/>
  </qemu:commandline>
</domain>

 

Any other ideas?

[tayshun12]

It looks like from your devices you have 1 dedicated graphics card but correct me if i'm wrong. I'm also seeing:

0a:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 21)

Which I am assuming is your integrated graphics?

 

If this is the case, make sure that your BIOS selects the integrated GPU and not the dedicated one. When this is done correctly you should NOT see the unRAID terminal when your monitor is plugged into your Dedicated graphics.

 

If you currently see the terminal screen and your monitor is plugged into your 610, that means unRAID is using it and the only way you can access your VM is through VNC.

 

Let me know!

 

T

[goober07]

01:00.0 VGA

01:00.1 HDMI Audio

 

Try a new VM using the web UI and make sure to pass both of these devices through. Passing a nvidia VGA controller without the associated audio device has caused problems for several of us.

 

Sorry if you've already tried this - hard to read your xml on my phone...

 

[jonp]

The 550ti for us always worked once when the VM was first booted, but if you rebooted the VM, the graphics wouldn't reinitialize and would render a code 10 error if you remote in using VNC or RDP. This is an issue with the card and not something we can solve.  Please obtain a newer / better GPU for this.

[stratigary]

Jon,

 

Thanks for the reply.  I actually did replace it with the Geforce GT 610 and, while I think I solved the Code 10 issue by passing the HDMI audio through, I know have an issue with rebooting.  Here is what I did:

 

1) Deleted previous VM

2) Recreated new Win 10 VM using video and instructions you made

3) Used VNC to install basic drivers

3) Passed through GT 610 and HDMI audio to VM, installed drivers, everything was fine.

4) Reboot to see if everything persists.

 

As soon as I reboot from the VM, the VM and Unraid itself hangs at the windows loading screen.  I physically have to reboot my server to get it working again.

 

Can I reboot from the VM or do I need to restart via the GUI?

 

The 550ti for us always worked once when the VM was first booted, but if you rebooted the VM, the graphics wouldn't reinitialize and would render a code 10 error if you remote in using VNC or RDP. This is an issue with the card and not something we can solve.  Please obtain a newer / better GPU for this.

[stratigary]

Thanks for all the input and help everyone, but I think I'm giving up on the idea of using unraid to run a VM. 

 

I've tried everything under the sun and come to the conclusion that it just isn't possible to run a stable instance of Windows 10 as a VM.  I've been troubleshooting for 3 weeks and am beyond frustrated.  No matter what I try I can only get it to work for one reboot and then it locks up the entire system, including unraid, and forces an unclean shutdown. I've moved PCI slots, recreated VM's multiple times, moved mouse and keyboard to separate USB PCI card, tried suggested xml edits all with limited/no success.

 

The closest I came is when I recreated a new VM, setup as usual, then passed through the GT 610 AND HDMI sound even though I'm not using the HDMI port (using dual DVI).  The problem is then I can't use my PCI sound card because they conflict if I try to pass that card through.  Even without the PCI sound card it only ran stable for 2 reboots before it locked up the system.

 

I really do love unraid as a whole and it does what it is supposed to do without fail.  I was just hoping to lower my energy footprint by combining two systems as I didn't use my separate workstation much anymore.  Maybe when 6.2 is released I might take another stab at it to see if the VM part of this is more stable and intuitive.

 

Thanks again!

[tayshun12]

Sorry to hear that you're wanting to give up!

 

By any chance have you tried installing another OS or just windows 10?

[stratigary]

Sorry to hear that you're wanting to give up!

 

By any chance have you tried installing another OS or just windows 10?

 

It's not that I really want to give up for now, I've just been without a working desktop for three weeks and need to get some work done   I'll probably give it another shot when 6.2 is released and see how that works.  I'll also be scouring the forums in the meantime to learn more and see if I can find out what's going wrong.

 

I did install a working copy of Windows 8.1 but, to be honest, I can't stand 8.1 at all.  I really don't want to revert back to 7 either.  I'm pretty sure this has to be an issue with Windows 10.

[tayshun12]

Well glad to hear you're willing to try agian! I wouldn't use 8.1 either to be honest, and I understand not wanting to revert back to 7.

 

Best of luck in the future!

 

T

[goober07]

On March 4th I wrote that the 610 will probably not work without the HDMI audio passed through as well. Doesn't matter if you intend to use it or not, it needs passed through. With the iommu groups and devices you posted, this should work (you mentioned a conflict with a sound card - that doesn't make sense given the groups & devices you posted originally). Something else must be going on. It's not impossible that your specific 610 just doesn't like resetting properly and you'll need to move on to a 3rd gpu...

 

Did you physically remove all other pcie cards to troubleshoot just the 610? And I know you're frustrated and say you've tried everything. Does that include bios updates? All the combos of Seabios+I440, Seabios+Q35, OVMF+i440? ACS override (if, for example, your sound card ended up grouped with another device)? Last I read, OVMF+Q35 had known issues.

 

It took over a month to get my system "right." I was having issues that the general population didn't seem to experience. Once we got it, though, it really is quite enjoyable.

[stratigary]

On March 4th I wrote that the 610 will probably not work without the HDMI audio passed through as well. Doesn't matter if you intend to use it or not, it needs passed through

 

That tip was quite helpful actually, as it gave me the most stable version thus far.  For some reason, even with that fix the VM would start hanging at the windows loading screen after about 2 reboots of the VM.  Unfortunately, passing though the HDMI audio (which I can't use as I'm rulling dual DVI) also means I can't pass through my PCI audio card meaning no sound at all.

 

Did you physically remove all other pcie cards to troubleshoot just the 610? And I know you're frustrated and say you've tried everything. Does that include bios updates?

 

I did remove all the pcie cards with no change in stability to the VM.  I also made sure that the bios was up to date as well.

 

All the combos of Seabios+I440, Seabios+Q35, OVMF+i440? ACS override (if, for example, your sound card ended up grouped with another device)? Last I read, OVMF+Q35 had known issues.

 

I'm pretty new when it comes to tinkering with VM's so I just found out about those combos you mentioned and I honestly have not much of a clue as to what they are and how they would affect my system.  I've seen them before in the advanced settings of the VM manager, but I've always just used the default settings which I believe is the Seabios+I440.  Would you suggest trying any other specific combo?

 

The biggest reason I decided to put it off for now it the number of times the VM has locked up my entire server and forced a unclean shutdown.  I'm not sure I want to risk any data corruption or other issues with unraid itself over the problems I'm having.  I think I can still return this video card to Amazon, so I might try a new getting a new one but that might be hard finding one that doesn't have HDMI audio to pass through.

[goober07]

My Windows 10 VM is using a 770GTX, OVMF and i440. It's worth trying. I didn't document the issues I experienced with Seabios, but I certainly had more than one forced parity check during my tinkering. I feel your pain.

 

Are you using the "latest" or "stable" virtio drivers? The unraid documentation says use "stable," but with Windows 10, I had to move to a newer version.

 

However, the biggest improvement on my build was eliminating USB passthrough. Correctly passing through a PCIe - USB3 card seemed to solve issues with Windows Update, rebooting, and latency.

 

You probably won't find a newer card that doesn't support HDMI these days... Or at least I don't see why you'd want to. The fact is it's such a pervasive standard (even if it's sole purpose is Holywood's DRM) that it just makes sense to support it.

 

What exactly prevents you from passing through a sound card in addition to the HDMI audio? Just click the green + in the webUI to add a "2nd sound card." IF that sound card is in an iommu grouo with another device, ACS override MAY be a work around for you - but that's totally unrelated to the HDMI audio.

[stratigary]

I think I'll give the Win 10 VM another shot today or tomorrow trying the OVMF and i440.  Right now I'm using the "stable" drivers, but will give the "latest" ones a go if it seemed to work for you.

 

I've been able to pass through my PCIe usb 3.0 card with good success and it does work much better overall than passing any USB devices through using the GUI.

 

Yea, the HDMI problem is one I seem to not be able to get around.  I have two older Dell IPS 24" IPS monitors that I use for photography and they don't have HDMI input, only DVI.  I love these things and don't plan on buying two new monitors anytime soon.

 

For some reason, it will not allow me to pass through the HDMI audio and the PCI sound card at the same time.  It's an older sound card and doesn't show up in the GUI, so I have to pass it through in the xml code and get start up errors when trying to do both.

 

I'll update with my findings on the new settings when I get a chance to try it.

[stratigary]

Well, I gave everything a shot but it still doesn't work

 

OVFM and i440 let me install Windows, but as soon as I reboot it throws me into some command line and refuses to boot into windows.  I read in the forum about a way to get it to boot from that command line, but that's impossible to do as it won't boot up using my graphics card to begin with.  Besides, that method just screams problems down the road.

 

Tried Seabios again with Q35 and, while I could get booted and video drivers installed, it will not pass through my USB 3.0 pcie card even though Windows detects it.  I get a code 10 error even after reinstalling drivers and no amount of moving the card or rebooting will get Windows to accept the card.  I can't use a mouse or keyboard without it.

 

Oh well, I really appreciate all the help but I think I'll just have to wait until the whole VM on unraid thing matures sometime down the road.