[threadripper "ugly patch"]

i have just built a 1950x system with a 108Ti and a 980Ti. i seem to not be able to get any VM to work with pass though, i have tried both without and with the patch and it is not working for me. hope there will be a fully working patch for this soon

[unable to start VM for Execution error]

well i was able to fix the problem, looks like the ACS was turned off on the system. big thanks to all that helped

[unable to start VM for Execution error]

Im 90% sure i was runing my my first GPU(980Ti) in passthrough mode fine without ACS on. I was thinking this morning it could be that the linux kernal might not have the driver for the 1080Ti and that is the problem, so i have pluged my 980Ti back in and stll having the same problem. I will try a difforent pci lane as im starting to think the second slot (16x) might be dead now.

 

If i have the 980Ti in the top pci 16x it seems ti work and the 1080Ti in the second pci 16x slot then it plays up. Unraid is running on the onboard video output so i dont think thats the problem. When i get home ill try ACS agen and see if that works. Hope it is not a dead pci slot

[unable to start VM for Execution error]

Hi everyone. i am having heaps of problems trying to boot my VM computer after installing a 1080Ti card in my pc. long story short, installed new GPU then the usb drive i was using would not boot,  replaced to s spare usb2 stick and all works good. when i assign the new GPU to the VM i keep getting a popup of "Execution error"

internal error: process exited while connecting to monitor: 2017-09-25T03:34:02.095343Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver.
2017-09-25T03:34:02.095361Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 1
2017-09-25T03:34:02.095368Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed

i have put the GPU in the GO file that i found people talking about to somehow allow it to be passed to the VM.

This is the XML file for the VM

<domain type='kvm'>
  <name>Windows 10 UEFI</name>
  <uuid>04bc150e-b2b4-88f3-8823-ca5fbecf34b9</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'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='4'/>
    <vcpupin vcpu='3' cpuset='5'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/04bc150e-b2b4-88f3-8823-ca5fbecf34b9_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='2' 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/VM HD/Windows 10 UEFI/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='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/VM HD/Windows 10 UEFI/vdisk2.img'/>
      <target dev='hdd' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
    <controller type='usb' index='0' model='nec-xhci'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <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:13:b0'/>
      <source bridge='br1'/>
      <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='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' 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='0x1c4f'/>
        <product id='0x0032'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x258a'/>
        <product id='0x0005'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </memballoon>
  </devices>
</domain>

Thanks to advance for the help

[UPS connection help]

On 10/03/2017 at 9:47 PM, mr-hexen said:

What about the NUT plugin ?

 

 

Thanks for all the help so fare. i was having a look around and found that the ups is designed as a Line-Interactive UPS, im note sure if that can help in finding the correct way to get unraid talking to it. I have also installed the windows software for it and i think there might be some .DLL driver files in there. im pritty sure windows drivers are not found in .DLL files

[UPS connection help]

i am thinking the model number is a MP5207 but i am not 100% on it. This is the website were the ups is and here is the link to the manual. this is pretty much what i can find on it and what i was given 

[UPS connection help]

I am having problems getting my ups working with my unraid setup. the ups is listed as a connected usb device as Fry's Electronics. I have tried every option under the UPS cable and UPS type all with the same message coming up saying "Lost communication".

 

anyone that can help with this problem would be great

[Audio problems with 750ti and Windows 10 vm]

sorry to bring a post back from the dead, i am having thr same problem with a 980Ti. i went to try get the app to fix this problem but it looks like the link is down. If anyone still has it could you please link me to were i could find it

 

Thanks