surfshack66

Hey guys. I'm unable to reach several dockers because of the error message below. Any ideas whats blocking the connection? The connection to '192.168.1.2' failed. Error: ConnectionRefused (0x274d). System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it 192.168.1.2:5050

Well that was the issue. I added that into the gui mode and the IOMMU groups reflected the change. Thanks for the help. This issue is solved.

If I boot into GUI mode, does this mean pcie_acs_override is disabled? default /syslinux/menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream pci-stub.ids=8086:10bc initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest Also, what is the default syslinux config? I edited this prior to the upgrade to stub the NIC but now it can be handled directly in the VM config

So the latest stable linux kernel is 4.7.5 as of 9/24. Do we plan on upgrading to that at some point? Is there even a way to test that upgrading the kernel with affect the IOMMU groups again? I have a workaround for now using the OS GUI and connecting to my windows vm via VNC, but its less than ideal. Any other suggestions/input?

Thanks @gridrunner Yes, I was on 6.1.9 before and I'm using an Intel i7-4790K.

Thanks for the tip. Unfortunately, it is on. Even worse, I changed the slot of the NIC and it remained in the same IOUMMU group. I'm not sure what to do at this point and I'm still confused why it changed after the upgrade. I also tried turning VMs off and rebooting but no luck. Any other way to force an IOMMU group change?

I've tried rebooting several times with the setting turned on and off but every time I go to the VM Manager settings. It says "You must reboot for changes to take effect". If I change the setting to no and "apply" the message disappears. If I change it from no to yes then apply the message appears, so I'll reboot but the message persists. Any ideas why this is happening?

Is there any way to change the IOMMU groups without physically moving the devices?

Thanks. Looks like the groups changed since updating from 6.1.9 to 6.2 because everything worked fine before that. Also, I had a similar issue before and turned the ACS override setting on, so it's odd that the groups combined again.

Error Message: Execution error Requested operation is not valid: PCI device 0000:04:00.0 is in use by driver QEMU, domain pfSense IOMMU groups: IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.1 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/1/devices/0000:03:02.0 /sys/kernel/iommu_groups/1/devices/0000:03:04.0 /sys/kernel/iommu_groups/1/devices/0000:04:00.0 /sys/kernel/iommu_groups/1/devices/0000:04:00.1 /sys/kernel/iommu_groups/1/devices/0000:05:00.0 /sys/kernel/iommu_groups/1/devices/0000:05:00.1 /sys/kernel/iommu_groups/2/devices/0000:00:02.0 /sys/kernel/iommu_groups/3/devices/0000:00:03.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.0 /sys/kernel/iommu_groups/5/devices/0000:00:16.0 /sys/kernel/iommu_groups/6/devices/0000:00:1a.0 /sys/kernel/iommu_groups/7/devices/0000:00:1b.0 /sys/kernel/iommu_groups/8/devices/0000:00:1c.0 /sys/kernel/iommu_groups/9/devices/0000:00:1c.3 /sys/kernel/iommu_groups/10/devices/0000:00:1c.5 /sys/kernel/iommu_groups/11/devices/0000:00:1d.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.2 /sys/kernel/iommu_groups/12/devices/0000:00:1f.3 /sys/kernel/iommu_groups/13/devices/0000:07:00.0 /sys/kernel/iommu_groups/14/devices/0000:08:00.0 PCI devices: PCI Devices 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) 00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller [8086:0c05] (rev 06) 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1] 00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba] 00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad] 00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0] 00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0) 00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0) 00:1c.5 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 6 [8086:8c9a] (rev d0) 00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6] 00:1f.0 ISA bridge [0601]: Intel Corporation 9 Series Chipset Family Z97 LPC Controller [8086:8cc4] 00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82] 00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1) 02:00.0 PCI bridge [0604]: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch [111d:8018] (rev 0e) 03:02.0 PCI bridge [0604]: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch [111d:8018] (rev 0e) 03:04.0 PCI bridge [0604]: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch [111d:8018] (rev 0e) 04:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06) 04:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06) 05:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06) 05:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06) 07:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 13) 08:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3] Windows 10 VM XML <domain type='kvm'> <name>Windows 10</name> <uuid>5452f3a7-e756-9635-6ed6-4296c1817b09</uuid> <description>Workstation</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </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='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor id='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/vdisks/Windows 10/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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows 10 Enterprise VL X64 v1511 en-US March 2016/W10Ent.VLX64.en-US.Mar2016.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.118-2.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='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' 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='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:08:6c:41'/> <source bridge='br0'/> <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'> <source mode='connect'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1af3'/> <product id='0x0001'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2516'/> <product id='0x0004'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> "Offending" VM XML: <domain type='kvm' id='2'> <name>pfSense</name> <uuid>bd84c85a-3e93-761c-ee2a-f9ae6e1d46c6</uuid> <description>pfSense Router / Firewall</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="linux.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vdisks/pfSense/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/pfSense-LiveCD-2.2.6-RELEASE-amd64-20151221-1450.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:30:ed:0d'/> <source bridge='virbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-pfSense/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' 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'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

Windows 10 VM can't start because a pci device is in use by driver QEMU (used in another VM). I'm confused why I'm receiving this error because im not using this particular pci device in this VM.

Ok, so I changed some of the VM settings i.e. machine type, hyper-v.. and that seemed to have cleared many of the previous errors. However, the last hurdle I face is "Requested operation is not valid: PCI device 0000:04:00.0 is in use by driver QEMU, domain pfSense". Not sure why I have this error though because this VM isn't using that PCI device?? EDIT: started new thread since the original issue is fixed. https://lime-technology.com/forum/index.php?topic=52285.0

Anyone have an idea?

Updating to the latest virtio drivers (118-2) didn't help unfortunately. Also, attached diagnostics. Any help would be greatly appreciated. tower-diagnostics-20160924-2134.zip

Hi - I'm receiving an execution error when trying to start my Win10 vm. Does anyone have some input? I should note that everything was working fine until I had a dynamix plugin issue (which I removed dynamix.plg) and rebooted. Upon reboot my webUI updated to 6.2 and now I have the vm issue. internal error: early end of file from monitor, possible problem: 2016-09-24T14:57:04.111958Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/14: Operation not permitted 2016-09-24T14:57:04.111974Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 14 2016-09-24T14:57:04.111979Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed Thanks, Angelo

Looks like I'm on 6.2 now, but the diagnostics are attached. Thanks again for the help. tower-diagnostics-20160924-1112.zip

First thing to do is to do plugins - check for updates, and install the dynamix webUI update available and then try the VM again Interestingly enough, the dynamic webUI is already up-to-date..

Thanks @Squid, that worked. However, I'm now unable to start my Windows 10 VM. Execution error internal error: early end of file from monitor, possible problem: 2016-09-24T14:57:04.111958Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/14: Operation not permitted 2016-09-24T14:57:04.111974Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 14 2016-09-24T14:57:04.111979Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed

Hi - The webgui isn't displaying due to a warning I am receiving. Anyone have some input? Thanks, Angelo

have you configured autotools by any chance? (see attachment), if you have then you need to make sure its set to /data/<folder of your choice> Negative, autotools are disabled ok so does /data/incomplete exist on your unraid host and can you see incomplete downloads in there? "/data/incomplete" doesn't specifically exist on my host but i mapped the /data folder to /mnt/user/media/downloads. however, i do see /incomplete within /mnt/user/media/downloads. I do see something interesting though. I downloaded a movie and it went to /mnt/user/media/downloads/incomplete. Great. I'm currently trying to download a tv show and its going to the docker img according to find /var/lib/docker/btrfs -type f -size +50000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }' , but it also has a label "TV" whereas the movie did not have a label. Ill see if that has anything to do with it. ok so it probably is related to adding a label then, have you configured the unpack settings by any chance? (see attachment) this also allows you to define a different path, if its blank i would recommend setting this to your incomplete folder, so /data/incomplete so it wasnt related to the label, however, sonarr was incorrectly configured. sorry for the confusion and thanks for the help.

have you configured autotools by any chance? (see attachment), if you have then you need to make sure its set to /data/<folder of your choice> Negative, autotools are disabled ok so does /data/incomplete exist on your unraid host and can you see incomplete downloads in there? "/data/incomplete" doesn't specifically exist on my host but i mapped the /data folder to /mnt/user/media/downloads. however, i do see /incomplete within /mnt/user/media/downloads. I do see something interesting though. I downloaded a movie and it went to /mnt/user/media/downloads/incomplete. Great. I'm currently trying to download a tv show and its going to the docker img according to find /var/lib/docker/btrfs -type f -size +50000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }' , but it also has a label "TV" whereas the movie did not have a label. Ill see if that has anything to do with it.

have you configured autotools by any chance? (see attachment), if you have then you need to make sure its set to /data/<folder of your choice> Negative, autotools are disabled

http://lime-technology.com/forum/index.php?topic=40937.msg405070#msg405070 Thanks. I checked the downloads location and its pointing to the correct directory. Is there a temp folder rtorrent uses?

Hi binhex - This docker is awesome. Thanks for developing it. I'm having some trouble with the docker image growing full as I download torrents. Any suggestions? Thanks

Thanks, @Squid!