spotopolis

I wanted to chime in here and I am having the same issue. My VM that is freezing is the latest version of PfSense (FreeBSD) that is locking up. No response from the console/ssh or the firewalls WebGUI. Nothing in the VMs logs or in UNRAIDS logs (even using the Enhanced Logs plugin). The only thing that kind of stood out to me was looking in the system processes in UNRAID, PfSense was recorded as using near half of my servers CPU resources (47% of my 24 total cores) . Im running a dual Xeon X5670 system but have VM CPU Pinning enabled for it ( cores/threads 8, 9, and 20, 21 ) Im not sure why its listed so high. In the VM, the PfSense WebGUI dash its only reporting 7%-10% CPU usage while the UNRAID Dashboard is reporting roughly the same for those cores. The update times look to be more frequent in the UNRAID dash, and I do see some quick jumps occasionally to around 40% on each of those 4 cores, but then falls right back down to single digit numbers. Is the 47% usage I'm seeing in the UNRAID logs reporting it as 47% of the 4 cores I have pinned, or is it reporting 47% of the 24 total cores in the system? I have another VM running Windows 8.1 Pro, with 4 cores pinned to it, and it has not frozen ever. I've only just had the PfSense VM freeze on me, and this is maybe the 2nd or 3rd time in 6 months to a year it has happened. The PfSense VM is my Firewall/Router for the whole house. When It freezes, I lose WAN connection, but my static LAN connections are all still working. I tried just restarting it from the VM popup menu in UNRAID and it didn't do anything. I had do Stop and Start the VM for it to come back up.

Necro again. But good job team.

I started getting warnings about machine check errors within the last few weeks. I installed the plugin from NerdPack that FixCommonProblems suggested and have attached my diagnostics output. From what I can tell, it may be pointing to a memory error, but I am not sure. Any help would be great. tower-diagnostics-20190222-1104.zip

So far so good! Just rebooted the VM due to the video driver update. Thank you for the help.

One last question. Will I need to reboot the unRAID box after adding the line or just try and start the VM again?

The bios for my system is up to date. Not the issue unfortunately. This is what my syslinux.cfg looks like. Do I add your line after "downstream" or after "bzroot"? default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest label Xen/unRAID OS kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot label Xen/unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode

Its still showing as Enabled.

Now after the ACS set to YES and a reboot, I am getting a group 15 error. internal error: early end of file from monitor: possible problem: 2015-09-25T17:44:03.870643Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2015-09-25T17:44:03.870672Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 15 2015-09-25T17:44:03.870680Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 15 2015-09-25T17:44:03.870691Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2015-09-25T17:44:03.870701Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized Here is the list of my IOMMU Groups. If I understand it correctly, group 15, the GPU, is no longer in a shared group if that was the issue before. /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:03.0 /sys/kernel/iommu_groups/3/devices/0000:00:07.0 /sys/kernel/iommu_groups/4/devices/0000:00:10.0 /sys/kernel/iommu_groups/4/devices/0000:00:10.1 /sys/kernel/iommu_groups/5/devices/0000:00:11.0 /sys/kernel/iommu_groups/5/devices/0000:00:11.1 /sys/kernel/iommu_groups/6/devices/0000:00:14.0 /sys/kernel/iommu_groups/6/devices/0000:00:14.1 /sys/kernel/iommu_groups/6/devices/0000:00:14.2 /sys/kernel/iommu_groups/7/devices/0000:00:15.0 /sys/kernel/iommu_groups/8/devices/0000:00:1a.0 /sys/kernel/iommu_groups/8/devices/0000:00:1a.1 /sys/kernel/iommu_groups/8/devices/0000:00:1a.2 /sys/kernel/iommu_groups/8/devices/0000:00:1a.7 /sys/kernel/iommu_groups/9/devices/0000:00:1b.0 /sys/kernel/iommu_groups/10/devices/0000:00:1c.0 /sys/kernel/iommu_groups/11/devices/0000:00:1c.5 /sys/kernel/iommu_groups/12/devices/0000:00:1d.0 /sys/kernel/iommu_groups/12/devices/0000:00:1d.1 /sys/kernel/iommu_groups/12/devices/0000:00:1d.2 /sys/kernel/iommu_groups/12/devices/0000:00:1d.7 /sys/kernel/iommu_groups/13/devices/0000:00:1e.0 /sys/kernel/iommu_groups/13/devices/0000:37:05.0 /sys/kernel/iommu_groups/14/devices/0000:00:1f.0 /sys/kernel/iommu_groups/14/devices/0000:00:1f.2 /sys/kernel/iommu_groups/15/devices/0000:0f:00.0 /sys/kernel/iommu_groups/16/devices/0000:01:00.0 /sys/kernel/iommu_groups/17/devices/0000:3f:00.0 /sys/kernel/iommu_groups/17/devices/0000:3f:00.1 /sys/kernel/iommu_groups/18/devices/0000:3f:02.0 /sys/kernel/iommu_groups/18/devices/0000:3f:02.1 /sys/kernel/iommu_groups/19/devices/0000:3f:03.0 /sys/kernel/iommu_groups/19/devices/0000:3f:03.1 /sys/kernel/iommu_groups/19/devices/0000:3f:03.4 /sys/kernel/iommu_groups/20/devices/0000:3f:04.0 /sys/kernel/iommu_groups/20/devices/0000:3f:04.1 /sys/kernel/iommu_groups/20/devices/0000:3f:04.2 /sys/kernel/iommu_groups/20/devices/0000:3f:04.3 /sys/kernel/iommu_groups/21/devices/0000:3f:05.0 /sys/kernel/iommu_groups/21/devices/0000:3f:05.1 /sys/kernel/iommu_groups/21/devices/0000:3f:05.2 /sys/kernel/iommu_groups/21/devices/0000:3f:05.3 /sys/kernel/iommu_groups/22/devices/0000:3f:06.0 /sys/kernel/iommu_groups/22/devices/0000:3f:06.1 /sys/kernel/iommu_groups/22/devices/0000:3f:06.2 /sys/kernel/iommu_groups/22/devices/0000:3f:06.3

Hmm... Okay. Im looking into it now. Im only using my server for basically 2 things: A Plex MS using Phaze's plugin, and a single VM. Ill trying out the ACS Override now.

I can and have always booted my VM with just the VMC option. I try to select the GPU (Quadro NVS 295) and hit update and that works, but then when I try to start the VM, unRAID gives me an error (not in the VM) Execution error internal error: early end of file from monitor: possible problem: 2015-09-25T17:20:19.578593Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2015-09-25T17:20:19.578628Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 14 2015-09-25T17:20:19.578638Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 14 2015-09-25T17:20:19.578651Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2015-09-25T17:20:19.578663Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized If I go back to just the VNC option it works fine again. Im not sure what I need to do. I havent found any other issues like this on the forum. All I see are the error 43's inside Windows once the VM boots.

Thats awesome. The downside is (for me anyway) Im running a vanilla dedicated server (without TShock). But the deeper I go into getting this server up and running it looks like I may have to start using it. Another issue is that you have to wait for TShock to be updated once an official Terraria patch has been released.

Thanks for the info. I was wanting to only run the Dedicated Server software witch dose not require any graphics drivers at all. Its just a command prompt based server while the client still handles all the rendering. Steam is not even needed for it and there are Win/Mac/Linux versions of the Standalone Dedicated Server. Would it be possible to build one just for that? Maybe even a super light Ubuntu Docker just to run the server console?

So I found this thread on the Official Terraria.org forums http://forums.terraria.org/index.php?threads/released-play-on-linux-docker-wine-steam.18742/ I wanted to know if it was possible to run something like this in UNRAID? Right now I am running a dedicated server through the UNRAID VM system. I have a full Windows 7x86 installed just to run the small dedicated server. I thought if I had a Docker that could run Terraria that it would use a lot less system resources. The link has the link to the GIT for the Docker file, but if I add it to the Docker list, it doesn't show up in the Templates. Am I just barking up the wrong tree here? Im new to Docker. So any input would be great.

I just set this up and using stock settings im only getting 25kb download speeds. it doesnt matter what torrent i am downloading. I tried setting the DL speed to 0 and to 999999 but it maxs out at 100kb/s. I havent changed any other options. Am I missing something?

Try clearing your browser cache. In Firefox it's Ctrl F5. HERP DERP!!! That did it. Im at the log in screen. Thank you for the help! Haha I almost always hit Ctrl F5 anymore. Do I still need to edit the GO file if the username vbox and pass dont get me in? Nevermind. Disabled the login in config.php. Thanks again for the help.