GoudaK

Well for some reason I come home to find all error logs stopped and parity build humming along nicely... I thought I stopped it but clearly didn't... I will wait for parity rebuild to complete (5 hours left) update firmware and go from there. Thanks for the help so far.

I'll grab full diagnostic when I get home this arvo. I should have noted all disks are currently on the motherboard to rule out the LSI card, should I update firmware and then move the 2 offending disks back to the LSI card?

I have again reseated cables with np effect.

So I have rebooted and now keep getting sata link resets... Feb 6 12:10:54 Tower kernel: ata6: SError: { RecovComm HostInt PHYRdyChg PHYInt } Feb 6 12:10:54 Tower kernel: ata6.00: failed command: READ DMA EXT Feb 6 12:10:54 Tower kernel: ata6.00: cmd 25/00:f8:08:04:1b/00:03:00:00:00/e0 tag 19 dma 520192 in Feb 6 12:10:54 Tower kernel: res 50/00:00:07:04:1b/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) Feb 6 12:10:54 Tower kernel: ata6.00: status: { DRDY } Feb 6 12:10:54 Tower kernel: ata6: hard resetting link Feb 6 12:10:55 Tower kernel: ata6: SATA link down (SStatus 0 SControl 320) Feb 6 12:10:57 Tower kernel: ata6: hard resetting link Feb 6 12:10:57 Tower kernel: ata6: SATA link down (SStatus 0 SControl 320) Feb 6 12:10:59 Tower kernel: ata6: hard resetting link Feb 6 12:11:04 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Feb 6 12:11:07 Tower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 6 12:11:07 Tower kernel: ata6.00: configured for UDMA/100 Feb 6 12:11:07 Tower kernel: ata6: EH complete Feb 6 12:11:07 Tower kernel: ata7.00: exception Emask 0x50 SAct 0x0 SErr 0x30802 action 0xe frozen Feb 6 12:11:07 Tower kernel: ata7.00: irq_stat 0x00400000, PHY RDY changed Feb 6 12:11:07 Tower kernel: ata7: SError: { RecovComm HostInt PHYRdyChg PHYInt } Feb 6 12:11:07 Tower kernel: ata7.00: failed command: READ DMA EXT Feb 6 12:11:07 Tower kernel: ata7.00: cmd 25/00:08:08:30:1b/00:04:00:00:00/e0 tag 6 dma 528384 in Feb 6 12:11:07 Tower kernel: res 50/00:00:07:30:1b/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) Feb 6 12:11:07 Tower kernel: ata7.00: status: { DRDY } Feb 6 12:11:07 Tower kernel: ata7: hard resetting link Feb 6 12:11:08 Tower kernel: ata7: SATA link down (SStatus 0 SControl 310) Feb 6 12:11:10 Tower kernel: ata7: hard resetting link Feb 6 12:11:10 Tower kernel: ata7: SATA link down (SStatus 0 SControl 310) Feb 6 12:11:11 Tower kernel: ata7: hard resetting link Feb 6 12:11:20 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 6 12:11:20 Tower kernel: ata7.00: configured for UDMA/33 Feb 6 12:11:20 Tower kernel: ata7: EH complete Feb 6 12:11:20 Tower kernel: ata7.00: exception Emask 0x50 SAct 0x0 SErr 0x30802 action 0xe frozen Feb 6 12:11:20 Tower kernel: ata7.00: irq_stat 0x00400000, PHY RDY changed Feb 6 12:11:20 Tower kernel: ata7: SError: { RecovComm HostInt PHYRdyChg PHYInt } Feb 6 12:11:20 Tower kernel: ata7.00: failed command: READ DMA EXT Feb 6 12:11:20 Tower kernel: ata7.00: cmd 25/00:f8:08:d8:1b/00:03:00:00:00/e0 tag 8 dma 520192 in Feb 6 12:11:20 Tower kernel: res 50/00:00:07:d8:1b/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) Feb 6 12:11:20 Tower kernel: ata7.00: status: { DRDY } Feb 6 12:11:20 Tower kernel: ata7: hard resetting link Feb 6 12:11:21 Tower kernel: ata7: SATA link down (SStatus 0 SControl 310) Feb 6 12:11:23 Tower kernel: ata7: hard resetting link Feb 6 12:11:23 Tower kernel: ata7: SATA link down (SStatus 0 SControl 310) Feb 6 12:11:24 Tower kernel: ata7: hard resetting link

Thanks Johnnie, I realised too late it was causing issues. I've disabled and will reboot and report back.

I should also note, as soon as a drive failed I proceeded to preclear it for a second time ensuring not to physically move it, the resulting preclear and post read was successful.

Thank you for your reply. I have checked that, have plugged and unplugged them in a number of times also. At one point I had 2 rows of 4 drives, on one row there was 2x Toshiba drives, 1 Seagate and 1 HGST the Toshiba drives were still causing issues the other 2 drives have not had any issues at all. The other row has 4 Toshiba drives. I am using molex to 4x sata breakout cables both running off separate rails off the PSU. The PSU is a 1200w Silverstone Gold PSU.

tower-diagnostics-20190205-1216.zipHello, I'm having some very frusterating problems with Disks dropping from the array with read errors. They are specific to a set of brand new drive I have purchased, each drive was precleared prior to entering the array with no SMART errors. I purchased 10 Toshiba 8tb drives to begin replacing some aging disks, as soon as I started adding the disks to the array I was having problems, initially the XFS filesystem was becoming corrupt and unable to be repaired, I removed the offending drives and used UFS Explorer to recover all the data successfully. I have now backed up all my data on separate drives and have started a completely new array. With the trial and error restoring my files from backups it seems as soon as one of the drives fills up to 4.03TB I start getting disk read errors. I have managed to get one drive to start filling past the 4.03tb mark, however this was by transferring directly to the disk share rather than the user share (again through trial and error). Obviously this isn't the intended used case however I am trying to understand what the root cause is. One of the disks I am pre-clearing is also being limited to 1.5gbs with these errors showing: Feb 4 03:15:36 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 4 03:15:36 Tower kernel: ata3.00: ATA-10: TOSHIBA MG05ACA800E, Z6LGK004FXJD, GX0R, max UDMA/100 Feb 4 03:15:36 Tower kernel: ata3.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA Feb 4 03:15:36 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:15:36 Tower kernel: sd 3:0:0:0: [sdk] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Feb 4 03:15:36 Tower kernel: sd 3:0:0:0: [sdk] 4096-byte physical blocks Feb 4 03:15:36 Tower kernel: sd 3:0:0:0: [sdk] Write Protect is off Feb 4 03:15:36 Tower kernel: sd 3:0:0:0: [sdk] Mode Sense: 00 3a 00 00 Feb 4 03:15:36 Tower kernel: sd 3:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 4 03:15:36 Tower kernel: ata3.00: exception Emask 0x50 SAct 0x20000 SErr 0xb0802 action 0xe frozen Feb 4 03:15:36 Tower kernel: ata3.00: irq_stat 0x00400000, PHY RDY changed Feb 4 03:15:36 Tower kernel: ata3: SError: { RecovComm HostInt PHYRdyChg PHYInt 10B8B } Feb 4 03:15:36 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Feb 4 03:15:36 Tower kernel: ata3.00: cmd 60/08:88:00:00:00/00:00:00:00:00/40 tag 17 ncq dma 4096 in Feb 4 03:15:36 Tower kernel: ata3.00: status: { DRDY } Feb 4 03:15:36 Tower kernel: ata3: hard resetting link Feb 4 03:15:42 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 4 03:15:42 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:15:42 Tower kernel: ata3: EH complete Feb 4 03:15:42 Tower kernel: sdk: sdk1 Feb 4 03:15:42 Tower kernel: sd 3:0:0:0: [sdk] Attached SCSI disk Feb 4 03:15:44 Tower kernel: ata3: SATA link down (SStatus 0 SControl 300) Feb 4 03:15:56 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 4 03:15:56 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:16:03 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 4 03:16:03 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:16:04 Tower kernel: ata3: limiting SATA link speed to 3.0 Gbps Feb 4 03:16:10 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 4 03:16:10 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:16:17 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 4 03:16:17 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:16:24 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 4 03:16:24 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:16:31 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 4 03:16:31 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:16:32 Tower kernel: ata3: limiting SATA link speed to 1.5 Gbps Feb 4 03:16:39 Tower kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 4 03:16:39 Tower kernel: ata3.00: configured for UDMA/100 Feb 4 03:16:47 Tower kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 4 03:16:47 Tower kernel: ata3.00: configured for UDMA/100 Again this disk is brand new and passes SMART scans. I did read there were some Linux Kernel bugs with certain drives and SATA controllers, however I have tried with my motherboard onboard sata ports and my LSI 9260-8i, both having the same results. My motherboard is a Gigabyte X399 board with a Treadripper 1900x. Have also ensured to seat and re-seat cables and try different cables. I have attached full diagnostics below. Hoping someone is going to point out where I have done something incredibly stupid and help resolve the issue for me because at this point I am ready to give up.

Sure is, all you need to do is transfer the meta data to the docker folder from the windows folder. It's the same folder structure. The transfer will take a very long time as it is thousands of little files... Mine too 34 hours.

Well I still have no fix, I have put the crappy GPU (GT510) back in slot 1, moved the 1080ti to slot 3 and am able to pass that through. I still can't see the GT510 in the list to select for a VM so I am really not sure what is going on.

Anyone?

Throwing an idea out there... My motherboard does not have on board graphics, this is the only thing that I can think of that may be different to the setup (in a very broad sense) to Spaceinvaders? This means unraid may not be able to obtain another video output? Thoughts? Edit - now that I think of it I've only ever seen the 980ti available for selection for a VM, the card in the first slot was never visible in the drop down.

Hi All, I am trying to pass an NVIDIA GPU in slot 1 to a VM, I am following this guide from Spaceinvader One: I have followed the video by downloading and editing the BIOS, moving the BIOS file to unRAID, however I cannot see the GPU as available to select in the VM config, it only shows VNC... The GPU also isn't showing as a system device however will display the unRAID boot sequence so I am certain the card is working. I previously had this VM working with a passed through 980ti, which was in the 3RD PCIe slot, I am upgrading to a 1080ti and decided to remove the gpu from slot 1 and install the 1080ti in slot one to reduce number of cards. Any ideas? Here is the IOMMU list: 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.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 4: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 5: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host 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 [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 [1022:145a] 09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a [1022:1456] 09:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:145c] 09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 8: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [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 [1022:1455] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 [1022:7901] 0a:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [1022:1457] 0a:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller IOMMU group 9: [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 10: [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 11: [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 12: [1022:43ba] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset USB 3.1 xHCI Controller (rev 02) [1022:43b6] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller (rev 02) [1022:43b1] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset PCIe Bridge (rev 02) [1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1b21:1343] 03:00.0 USB controller: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [8086:24fd] 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) [1969:e0b1] 05:00.0 Ethernet controller: Qualcomm Atheros Killer E2500 Gigabit Ethernet Controller (rev 10) IOMMU group 13: [144d:a802] 07:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 (rev 01) IOMMU group 14: [1106:3483] 08:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01)

I solved it by using a USB3 PCIE card... I cannot explain why that works...

After a lot of mucking around it appears to be my USB headset... As soon as I pass my Astro A50 headset the VM will not boot or if I hot plug the VM becomes unresponsive. I have tried this with 2 separate VM's with the exact same result. The 4 cores attached to the VM go to 100% usage, as soon as I unplug the headset the VM is responsive and will boot. Any ideas?

Thanks, I'll give it a go... although with the new VM there were no Nvidia drivers installed at all and it refused to boot with GPU passthrough.

So I spun up another Windows VM using VNC, I updated to latest windows build and it was working fine, rebooted several times without issue. This morning I tried to pass the GPU through and the VM will not boot with the same issue as above. All CPU cores assigned to the VM are maxed at 100%, however no booting will occur. I tried the original VM without GPU pass through and it boots fine. I've now updated this to the latest Windows build, it will boot without GPU passed through however will not boot with it passed. Could this perhaps been caused by the unRAID update?

I’ve blocked the 1803 update and have successfully rebooted several times without issue... I can only pause the update for 35 days, is anyone else having these problems?

Hi all, I’m having a problem with what has been a stable Win10 VM. After the 6.5.3 unRAID update my VM will refuse to boot, it just stays on the circle loading screen and will not progress. There also seems to be a windows update happening which might also be causing the problem? If I start up repair the VM it will boot once and then refuse to boot again (installs 1803 downloaded update), everything works except chrome when I get in once. My mate is having exactly the same drama as me also. Has anyone got a clue on what’s happening here? [EDIT] After a lot of mucking around it appears to be my USB headset... As soon as I pass my Astro A50 headset the VM will not boot or if I hot plug the VM becomes unresponsive. I have tried this with 2 separate VM's with the exact same result. The 4 cores attached to the VM go to 100% usage, as soon as I unplug the headset the VM is responsive and will boot. I have tried with a passed through USB3 card, hotplug via Libvert Hotplug and assigning to the VM both in the USB3 card and motherboard directly. This has been working fine for about 12 months and now refuses, any ideas? Here are the logs: 2018-06-19 09:21:35.003+0000: shutting down, reason=failed 2018-06-19 09:22:06.164+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Tower 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-2-Windows 10/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -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/994d5b83-a351-3957-4b44-22794ad79b0b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 994d5b83-a351-3957-4b44-22794ad79b0b -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device icvice virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:f7:e0,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-2-Windows 10/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=09:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=09:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=7,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=7,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=7,hostaddr=4,id=hostdev4,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on 2018-06-19 09:22:06.164+0000: Domain id=2 is tainted: high-privileges 2018-06-19 09:22:06.164+0000: Domain id=2 is tainted: host-cpu 2018-06-19T09:22:06.197831Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) libusb: error [udev_hotplug_event] ignoring udev action bind libusb: error [op_set_configuration] failed, error -1 errno 110 2018-06-19T09:26:22.547059Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER] libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/5-1/bConfigurationValue failed ret=-1 errno=2 2018-06-19T09:27:47.873161Z qemu-system-x86_64: terminating on signal 15 from pid 11917 (/usr/sbin/libvirtd) 2018-06-19 09:27:49.273+0000: shutting down, reason=destroyed 2018-06-19 09:28:40.670+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Tower 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-3-Windows 10/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -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/994d5b83-a351-3957-4b44-22794ad79b0b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 994d5b83-a351-3957-4b44-22794ad79b0b -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device icvice virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:f7:e0,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-3-Windows 10/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=09:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=09:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=7,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=7,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=7,hostaddr=4,id=hostdev4,bus=usb.0,port=3 -device usb-host,hostbus=5,hostaddr=12,id=hostdev5,bus=usb.0,port=4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on 2018-06-19 09:28:40.670+0000: Domain id=3 is tainted: high-privileges 2018-06-19 09:28:40.670+0000: Domain id=3 is tainted: host-cpu 2018-06-19T09:28:40.707861Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) libusb: error [op_set_configuration] failed, error -1 errno 110 2018-06-19T09:28:56.147061Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER] 2018-06-19 09:30:06.755+0000: shutting down, reason=destroyed 2018-06-19 09:33:16.097+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Tower 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-4-Windows 10/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -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/994d5b83-a351-3957-4b44-22794ad79b0b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 994d5b83-a351-3957-4b44-22794ad79b0b -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-4-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device icvice virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:f7:e0,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-4-Windows 10/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=09:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=09:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=7,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=7,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=7,hostaddr=4,id=hostdev4,bus=usb.0,port=3 -device usb-host,hostbus=7,hostaddr=5,id=hostdev5,bus=usb.0,port=4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on 2018-06-19 09:33:16.097+0000: Domain id=4 is tainted: high-privileges 2018-06-19 09:33:16.097+0000: Domain id=4 is tainted: host-cpu 2018-06-19T09:33:16.133397Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) libusb: error [op_set_configuration] failed, error -1 errno 110 2018-06-19T09:33:31.091058Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER] libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/7-2/bConfigurationValue failed ret=-1 errno=2 libusb: error [udev_hotplug_event] ignoring udev action bind libusb: error [op_set_configuration] failed, error -1 errno 110 2018-06-19T09:39:21.299030Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER]

I am by no means an expert here, however I had the same issue, are you connecting via //tower/ or the IP address? Try whichever one you're not using, there is also a thread on these issues which fixed it for me, I will have a browse and see if I can find it.

Sorry to revive an old thread, did you find a solution to this? I am also having the same issue. I've used root, anon and other users to no success.

I have build a Win10 VM using the guides from SpaceInvader One (thank you!) Despite following the steps in his videos I seem to be not getting even close to bare metal performance and I am unsure why. I have a 980ti, which was used in a Windows build prior to moving to unRAID on the same hardware and I seem to be getting a significant performance reduction. I've done some testing in PubG, pre VM I was able to run 4k @ 53 - 59 FPS. In the VM I get 25 - 32 FPS on the same settings. Dropping down to 1440p and on High I only get 45 - 47 FPS... I expected some performance drop however this is quite significant. CPU usage is always <50%, so its not a CPU bottleneck from what I can see. Its a Threadripper build with 1900x 4 cores 8 threads passed to the VM, 32gb DDR4 with 16gb passed to the VM. I tried emulating the CPU's as per advice in another thread and this absolutely killed CPU performance pegging it at 100%, effectively making the VM unusable. Does anyone have any other ideas?

Hi guys... I can't for the life of me figure out how to fix this error... any ideas? Using PIA VPN, transferred the .ovpn (same as the deluge install this is replacing). This seems to be stopping any torrents from connecting to peers... 018/05/13 07:54:24 [error] 941#941: *1 FastCGI sent in stderr: "PHP message: PHP Warning: fopen(/usr/share/webapps/rutorrent/share/settings/uisettings.json): failed to open stream: No such file or directory in /usr/share/webapps/rutorrent/php/getsettings.php on line 7" while reading response header from upstream, client: 192.168.1.24, server: localhost, request: "POST /php/getsettings.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "192.168.1.17:9080", referrer: "http://192.168.1.17:9080/"

Ah thank you very much! The VM will now start, however will not show any video output on the screen? I have unplugged the screen from the original GPU and now into my 980ti and nothing appears. I have tried both the HDMI and DP ports.

Here is the full diagnostics (attached). On the devices page it only shows up to iommu group 16, no group 18 shows, tower-diagnostics-20180427-0516.zip