Jump to content

jordanmw

Members
  • Posts

    288
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by jordanmw

  1. It seems that no matter what I do, I can't get the code 43 error to go away with passthrough GPUs.  I have 4 GTX960s and am trying to get a 4 gamers 1 cpu build going with my threadripper build.  Here is what I have:

    1920x threadripper

    X399 Asrock TaiChi (bios 3.20)

    1kw EVGA PSU

    64 Gb vengeance corsair RAM

    4x EVGA GTX960 SSC

     

    I have dumped the bios from those cards and am selecting the .rom file within the machine setup.  It does recognize the card- but will not load the driver with a code 43.  It obviously has something to do with not loading because it sees the virtual machine.  I need some help getting things going- and am willing to pay if needed.  This is driving me a little crazy since I went through the guide:

    https://forums.unraid.net/topic/69670-guide-fix-nvidia-code-43-issue-on-nvidia-gpu/

    and even got an older image of windows 10- but am still having problems. 

     

    I ran through the process in the guide with versions 388 and 411 but am having no luck installing- code 43 every time.

     

    System info:

    IOMMU group 0:[1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 1:[1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge

    IOMMU group 2:[1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge

    IOMMU group 3:[1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 4:[1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 5:[1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge

    IOMMU group 6:[1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 7:[1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 8:[1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B

    IOMMU group 9:[1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 10:[1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B

    IOMMU group 11:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)

    [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)

    IOMMU group 12:[1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0

    [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1

    [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2

    [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3

    [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4

    [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5

    [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6

    [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7

    IOMMU group 13:[1022:1460] 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0

    [1022:1461] 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1

    [1022:1462] 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2

    [1022:1463] 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3

    [1022:1464] 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4

    [1022:1465] 00:19.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5

    [1022:1466] 00:19.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6

    [1022:1467] 00:19.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7

    IOMMU group 14:[1022:43ba] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset USB 3.1 xHCI Controller (rev 02)

    IOMMU group 15:[1022:43b6] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller (rev 02)

    IOMMU group 16:[1022:43b1] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset PCIe Bridge (rev 02)

    IOMMU group 17:[1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)

    IOMMU group 18:[1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)

    IOMMU group 19:[1022:43b4] 02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)

    IOMMU group 20:[1022:43b4] 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)

    IOMMU group 21:[1022:43b4] 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)

    IOMMU group 22:[8086:1539] 04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

    IOMMU group 23:[8086:24fb] 05:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10)

    IOMMU group 24:[8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

    IOMMU group 25:[10de:1401] 08:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)

    IOMMU group 26:[10de:0fba] 08:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1)

    IOMMU group 27:[10de:1401] 09:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)

    IOMMU group 28:[10de:0fba] 09:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1)

    IOMMU group 29:[1022:145a] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a

    IOMMU group 30:[1022:1456] 0a:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor

    IOMMU group 31:[1022:145c] 0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller

    IOMMU group 32:[1022:1455] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455

    IOMMU group 33:[1022:7901] 0b:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

    IOMMU group 34:[1022:1457] 0b:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller

    IOMMU group 35:[1022:1452] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 36:[1022:1453] 40:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge

    IOMMU group 37:[1022:1452] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 38:[1022:1452] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 39:[1022:1453] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge

    IOMMU group 40:[1022:1452] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 41:[1022:1452] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 42:[1022:1454] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B

    IOMMU group 43:[1022:1452] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge

    IOMMU group 44:[1022:1454] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B

    IOMMU group 45:[10de:1401] 41:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)

    IOMMU group 46:[10de:0fba] 41:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1)

    IOMMU group 47:[10de:1401] 42:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)

    IOMMU group 48:[10de:0fba] 42:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1)

    IOMMU group 49:[1022:145a] 43:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a

    IOMMU group 50:[1022:1456] 43:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor

    IOMMU group 51:[1022:145c] 43:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller

    IOMMU group 52:[1022:1455] 44:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455

    IOMMU group 53:[1022:7901] 44:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

     

    CPU Thread Pairings

    Pair 1:cpu 0 / cpu 12

    Pair 2:cpu 1 / cpu 13

    Pair 3:cpu 2 / cpu 14

    Pair 4:cpu 3 / cpu 15

    Pair 5:cpu 4 / cpu 16

    Pair 6:cpu 5 / cpu 17

    Pair 7:cpu 6 / cpu 18

    Pair 8:cpu 7 / cpu 19

    Pair 9:cpu 8 / cpu 20

    Pair 10:cpu 9 / cpu 21

    Pair 11:cpu 10 / cpu 22

    Pair 12:cpu 11 / cpu 23

     

    USB Devices

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

    Bus 001 Device 002:ID 8087:0aa7 Intel Corp.

    Bus 001 Device 003:ID 2433:b200

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

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

    Bus 003 Device 002:ID 046d:c52b Logitech, Inc. Unifying Receiver

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

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

    Bus 005 Device 002:ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth

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

    Bus 006 Device 002:ID 0781:5583 SanDisk Corp. Ultra Fit

     

    SCSI Devices

    [0:0:0:0]disk SanDisk Ultra Fit 1.00 /dev/sda 30.7GB

    [1:0:0:0]disk ATA WDC WD30PURZ-85G 0A80 /dev/sdb 3.00TB

    [2:0:0:0]disk ATA WDC WD30EZRX-00M 0A80 /dev/sdc 3.00TB

    [5:0:0:0]disk ATA PLEXTOR PX-512S2 1.04 /dev/sdd 512GB

    [7:0:0:0]disk ATA WDC WD30EZRX-00M 0A80 /dev/sde 3.00TB

     

     

    VM XML:

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm'>
      <name>Windows 10-Lance</name>
      <uuid>d6c004a2-4090-d2c2-eeda-2ef31aae118c</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>10485760</memory>
      <currentMemory unit='KiB'>2097152</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>4</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='6'/>
        <vcpupin vcpu='1' cpuset='18'/>
        <vcpupin vcpu='2' cpuset='7'/>
        <vcpupin vcpu='3' cpuset='19'/>
      </cputune>
      <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/d6c004a2-4090-d2c2-eeda-2ef31aae118c_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='1234567890ab'/>
        </hyperv>
        <kvm>
          <hidden state='on'/>
        </kvm>
      </features>
      <cpu mode='host-passthrough' check='none'>
        <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-Lance/vdisk1.img'/>
          <target dev='hdc' bus='scsi'/>
          <boot order='1'/>
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/Win10_1607_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/isos/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='scsi' index='0' model='virtio-scsi'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
        </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='0x05' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:48:96:de'/>
          <source bridge='br0'/>
          <model type='virtio'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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'/>
        <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='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
        </video>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
          </source>
          <rom file='/mnt/disk1/isos/GM2061304.rom'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
        </hostdev>
        <memballoon model='virtio'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </memballoon>
      </devices>
    </domain>
     

    System Log:

    ct 2 11:51:50 Tower avahi-daemon[2580]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe48:96de.
    Oct 2 11:51:50 Tower kernel: br0: port 3(vnet0) entered disabled state
    Oct 2 11:51:50 Tower kernel: device vnet0 left promiscuous mode
    Oct 2 11:51:50 Tower kernel: br0: port 3(vnet0) entered disabled state
    Oct 2 11:51:50 Tower avahi-daemon[2580]: Withdrawing address record for fe80::fc54:ff:fe48:96de on vnet0.
    Oct 2 11:51:51 Tower kernel: vfio-pci 0000:08:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
    Oct 2 11:52:29 Tower kernel: vfio-pci 0000:08:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
    Oct 2 11:52:29 Tower kernel: br0: port 3(vnet0) entered blocking state
    Oct 2 11:52:29 Tower kernel: br0: port 3(vnet0) entered disabled state
    Oct 2 11:52:29 Tower kernel: device vnet0 entered promiscuous mode
    Oct 2 11:52:29 Tower kernel: br0: port 3(vnet0) entered blocking state
    Oct 2 11:52:29 Tower kernel: br0: port 3(vnet0) entered listening state
    Oct 2 11:52:31 Tower kernel: vfio_ecap_init: 0000:08:00.0 hiding ecap 0x1e@0x258
    Oct 2 11:52:31 Tower kernel: vfio_ecap_init: 0000:08:00.0 hiding ecap 0x19@0x900
    Oct 2 11:52:31 Tower avahi-daemon[2580]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe48:96de.
    Oct 2 11:52:31 Tower avahi-daemon[2580]: New relevant interface vnet0.IPv6 for mDNS.
    Oct 2 11:52:31 Tower avahi-daemon[2580]: Registering new address record for fe80::fc54:ff:fe48:96de on vnet0.*.
    Oct 2 11:52:31 Tower kernel: br0: port 3(vnet0) entered learning state
    Oct 2 11:52:33 Tower kernel: br0: port 3(vnet0) entered forwarding state
    Oct 2 11:52:33 Tower kernel: br0: topology change detected, propagating
    Oct 2 13:45:06 Tower avahi-daemon[2580]: Interface vnet0.IPv6 no longer relevant for mDNS.
    Oct 2 13:45:06 Tower avahi-daemon[2580]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe48:96de.
    Oct 2 13:45:06 Tower kernel: br0: port 3(vnet0) entered disabled state
    Oct 2 13:45:06 Tower kernel: device vnet0 left promiscuous mode
    Oct 2 13:45:06 Tower kernel: br0: port 3(vnet0) entered disabled state
    Oct 2 13:45:06 Tower avahi-daemon[2580]: Withdrawing address record for fe80::fc54:ff:fe48:96de on vnet0.
    Oct 2 13:45:07 Tower kernel: vfio-pci 0000:08:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
    Oct 2 13:46:16 Tower nginx: 2018/10/02 13:46:16 [error] 2634#2634: *87587 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 10.0.0.102, server: , request: "GET /plugins/dynamix.plugin.manager/scripts/plugin&arg1=install&arg2=http://lime-technology.com/forum/index.php?topic=36543.0 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "10.0.0.147", referrer: "http://10.0.0.147/Plugins"
    Oct 2 13:48:25 Tower emhttpd: req (3): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=install&arg2=https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.info.plg&csrf_token=****************
    Oct 2 13:48:25 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.info.plg
    Oct 2 13:48:54 Tower root: plugin: running: anonymous
    Oct 2 13:48:54 Tower root: plugin: creating: /boot/config/plugins/dynamix.system.info/dynamix.system.info.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.info.txz
    Oct 2 13:48:55 Tower root: plugin: checking: /boot/config/plugins/dynamix.system.info/dynamix.system.info.txz - MD5
    Oct 2 13:48:55 Tower root: plugin: running: /boot/config/plugins/dynamix.system.info/dynamix.system.info.txz
    Oct 2 13:48:55 Tower root: plugin: running: anonymous
    Oct 2 14:12:18 Tower kernel: kvm: already loaded the other module

     

    I did add some hyper-v and kvm edits to no avail.

     

    Any help would be very much appreciated.

     

    tower-diagnostics-20181002-1344.zip

    • Upvote 1
  2. I'm running into this issue also.  I even got the driver version that is mentioned in the guide.  Also downloaded the older 1607 windows build and still having no luck.  Are there setting that I need to add in the XML? Tried from reddit:

    <kvm>
      <hidden state='on'/>
    </kvm>

    Not seeing any change- still getting code 43 on every version of driver I try.  Anyone know how to vfio-pci the card? as steve asked... dead in the water with my 4 gpu setup.

     

    Has anyone had success with this since 388.0 versions?

  3. I did get a pcie extension cable and plan on mounting it on the PSU side of the case.  I have tested fit and it looks like it will stretch just far enough.  Not really worried about speed- just hot plug for the VMs.  I guess if it doesn't work- then I go with your suggestions of getting rid of it and just using the onboard controllers and assigning devices.  I didn't even think about that slot only providing a 1x pcie- thought it was 4x.  I'm not terribly concerned with access to the board. Thanks for the input- I'll let you know how it goes.

  4. Sounds like you have had similar challenges:

     

    I have finally committed to building a community gaming rig for my little tribe.  Most of the motivation is the pain I feel every time my brood brings their machines over for a gaming sesh.  I end up spending hours- troubleshooting, updating, and configuring- then barely get to play anything!  Drives me a little crazy- download 40GB of updates for everyone to be on the correct version- then figure out why XZY hardware/software isn't working.  I have run things like softxpand desktop to run 2 people on one machine but DRM doesn't like that setup very much.  I am on to a truly dedicated setup after watching several of the videos from the unraid community and linus. 

     

    The plan:

    Will run 6 machines if you include the host. 

    1x Unraid- 2 CPU cores 4HT 2Gb RAM

    1x Linux game server multi-host w/steamcache- 2 cores 4HT 8-12Gb RAM

    4x windows 10 gamers- 2 cores 4HT each 12Gb RAM each

     

    The hardware:

    Corsair 740 Air case

    Asrock Taichi X399

    Threadripper 1920X

    Corsair 64Gb 8x8Gb 2933Mhz

    Evga CLC 280

    Evga 1Kw gold PSU

    4x Evga GTX 960 SSC 4Gb (had them already- probably upgrade to 2XXX series eventually)

    2x Plextor 512Gb SSD

    2x WD purple 3Tb

     

    We aren't a finicky bunch- 1080p gaming with audio coming through our monitors is usually enough for us.  We play tons of different titles- old and new but usually avoid most of the AAA stuff until it's hit a steam sale.

    Favorites:

    7 days to die, dying light, TF2, No man's sky, Ark, borderlands games, L4D2, Warhammer Verminitde, Shadow warrior 2, far cry X, ect.....

     

    Thoughts and advice appreciated- I have all my hardware except my CPU- somehow missed the awesome amazon sale that had the 1920x for just over 300!! Just looking for one under $400 to complete the build and try my luck with unraid.

  5. I like the build- mine is pretty much built as a 4 gamer 1 pc setup but will have several machines for my home lab that will get spun up on demand.  Maybe you could give me some feedback- or warn me of the gotchas you ran into.

     

     

     

    The plan:

    Will run 6 machines if you include the host. 

    1x Unraid- 2 CPU cores 4HT 2Gb RAM

    1x Linux game server multi-host w/steamcache- 2 cores 4HT 8-12Gb RAM

    4x windows 10 gamers- 2 cores 4HT each 12Gb RAM each

    6x windows server test bench (only loading on demand)

     

    The hardware:

    Corsair 740 Air case

    Asrock Taichi X399

    Threadripper 1920X

    Corsair 64Gb 8x8Gb 2933Mhz

    Evga CLC 280

    Evga 1Kw gold PSU

    4x Evga GTX 960 SSC 4Gb (had them already- probably upgrade to 2XXX series eventually)

    Allegro pro 4x USB 3.0

    2x Plextor 512Gb SSD

    2x WD purple 3Tb

    Other random drives 2x250 SSD 2x2Tb HD

     

    We aren't a finicky bunch- 1080p gaming with audio coming through our monitors is usually enough for us.  We play tons of different titles- old and new but usually avoid most of the AAA stuff until it's hit a steam sale.

    Favorites:

    7 days to die, dying light, TF2, No man's sky, Ark, borderlands games, L4D2, Warhammer Verminitde, Shadow warrior 2, far cry X, ect.....

     

    Thoughts and advice appreciated- I have all my hardware except my CPU- (comes Wednesday)

     

     

     

  6. After watching the latest unraid video where linus installs the steamcache container for docker- I have finally committed to building a community gaming rig for my little tribe.  Most of the motivation is the pain I feel every time my brood brings their machines over for a gaming sesh.  I end up spending hours- troubleshooting, updating, and configuring- then barely get to play anything!  Drives me a little crazy- download 40GB of updates for everyone to be on the correct version- then figure out why XZY hardware/software isn't working.  I have run things like softxpand desktop to run 2 people on one machine but DRM doesn't like that setup very much.  I am on to a truly dedicated setup after watching several of the videos from the unraid community and linus. 

     

    The plan:

    Will run 6 machines if you include the host. 

    1x Unraid- 2 CPU cores 4HT 2Gb RAM

    1x Linux game server multi-host w/steamcache- 2 cores 4HT 8-12Gb RAM

    4x windows 10 gamers- 2 cores 4HT each 12Gb RAM each

     

    The hardware:

    Corsair 740 Air case

    Asrock Taichi X399

    Threadripper 1920X

    Corsair 64Gb 8x8Gb 2933Mhz

    Evga CLC 280

    Evga 1Kw gold PSU

    4x Evga GTX 960 SSC 4Gb (had them already- probably upgrade to 2XXX series eventually)

    2x Plextor 512Gb SSD

    2x WD purple 3Tb

     

    We aren't a finicky bunch- 1080p gaming with audio coming through our monitors is usually enough for us.  We play tons of different titles- old and new but usually avoid most of the AAA stuff until it's hit a steam sale.

    Favorites:

    7 days to die, dying light, TF2, No man's sky, Ark, borderlands games, L4D2, Warhammer Verminitde, Shadow warrior 2, far cry X, ect.....

     

    Thoughts and advice appreciated- I have all my hardware except my CPU- somehow missed the awesome amazon sale that had the 1920x for just over 300!! Just looking for one under $400 to complete the build and try my luck with unraid.

×
×
  • Create New...