Upgrading from 6.3.5 to 6.4 has caused major VM issues


Recommended Posts

Hi everyone, hopefully I'll cover everything because this is really starting to frustrate me. >:( tl;dr - Updating to 6.4 causes a VM to stutter like a bitch regardless of the content that is viewed on it.

 

I've been running UnRAID since early last year and its been great, no issues other than a few minor problems that were ironed out with MSI fixes for VMs and throwing a new GPU in to replace a failing one. I wanted to update to 6.4 to cover the Meltdown CPU exploits etc and thought everything would go fine, but I've got nothing but problems now.

 

Quick specs:

Sandisk Ultra 16GB USB drive for UnRAID 6.4 stable

SuperMicro X8DTH-6F (latest BIOS update 2.1b installed) + 1x Xeon X5670

32GB Hynix ECC RAM

Onboard SAS2008 and 1x Dell H310 flashed to IT for controllers

4x 4TB WD Red Drives

6x 3TB WD Red Drives

1x 250GB Samsung Evo SSD for Cache

1x Corsair Force SSD for VMs (2 VMs, one called "HTPC" and the other "Haruna")

nVidia GT710 passthrough to "HTPC" VM

2x Hauppauge WinTV-HVR-2200 TV Tuners passthrough to the "Haruna" VM

2x diagnostics files from my normal 6.4 and a fresh copy of 6.4 attached below

 

The two VMs both consist of Windows 10 x64 LTSB 2016 and are up to date - they both perform as per usual in terms of speed. The first VM I have (Haruna) runs fine, I use RDP to operate that one and run Windows only tasks that won't run in a Docker for example - so I'm unsure if it is showing the same problems as the second VM due to the lack of audio and GPU video (audio redirect is disabled).

 

The second VM (HTPC) is where all of my troubles are. I mostly use Kodi on this VM and some other light tasks. Intermittently, the VM will completely freeze up for a few seconds which causes a large amount of audio and video stutter - that makes watching any content a painful experience. This isn't the same "demonic sound" as running without the MSI fix though, but I double checked to make sure it's enabled anyway.

 

I've tried the following:

  • Tried variations of Q35 to i440fx, including newer and older versions
  • Made sure all device drivers are up to date, such as VirtIO drivers and especially the nVidia drivers
  • Removed some unneeded plugins and made sure all of the others are up to date, including Dockers
  • Tried disabling the C-States in the BIOS. If I leave them enabled, the server will  cease up which requires a forced restart (the built-in watchdog on the BIOS will also force a restart).

 

Since the very start though, I've always needed   vfio_iommu_type1.allow_unsafe_interrupts=1  appended to my syslinux.cfg in order to use the PCI-e devices as a passthrough, I assume this is because of the dated hardware - unsure if that has any bearing on any of this.

 

As a last ditch attempt, I even tried a new, fresh copy of 6.4 on a new, fresh USB drive - I only added Unassigned drives as a plugin to mount the VM SSD. I've attached the diagnostics of the fresh copy as well (yamato-diagnostics-20180119-0558).

 

This was all rock solid prior to the 6.4 update. Before I start losing sleep over this one and/or roll back to 6.3.5, are there any suggestions from the pros?

 

Thanks in advance.

yamato-diagnostics-20180119-2347.zip

yamato-diagnostics-20180119-0558.zip

Edited by Goldfire
Typos and more info
Link to comment

this in your logs maybe has something to do with it:

 

Jan 19 23:02:49 Yamato ntpd[1804]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

 

also uninstall the preclear plugin for now. it's causing other errors

 

an 19 23:20:15 Yamato nginx: 2018/01/19 23:20:15 [error] 10822#10822: *2656 FastCGI sent in stderr: "Unable to open primary script: /usr/local/emhttp/plugins/preclear.disk/Preclear.php (No such file or directory)" while reading response header from upstream, client: 192.168.1.148, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "http://192.168.1.5/Plugins"
Jan 19 23:20:16 Yamato nginx: 2018/01/19 23:20:16 [error] 10822#10822: *2656 FastCGI sent in stderr: "Unable to open primary script: /usr/local/emhttp/plugins/preclear.disk/Preclear.php (No such file or directory)" while reading response header from upstream, client: 192.168.1.148, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "http://192.168.1.5/Plugins"

 

Link to comment
9 hours ago, 1812 said:

this in your logs maybe has something to do with it:

 


Jan 19 23:02:49 Yamato ntpd[1804]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

 

Thanks for the reply.

Hm, isn't that simply for clock sync? Unless I'm missing something here?

 

9 hours ago, 1812 said:

also uninstall the preclear plugin for now. it's causing other errors

 


an 19 23:20:15 Yamato nginx: 2018/01/19 23:20:15 [error] 10822#10822: *2656 FastCGI sent in stderr: "Unable to open primary script: /usr/local/emhttp/plugins/preclear.disk/Preclear.php (No such file or directory)" while reading response header from upstream, client: 192.168.1.148, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "http://192.168.1.5/Plugins"
Jan 19 23:20:16 Yamato nginx: 2018/01/19 23:20:16 [error] 10822#10822: *2656 FastCGI sent in stderr: "Unable to open primary script: /usr/local/emhttp/plugins/preclear.disk/Preclear.php (No such file or directory)" while reading response header from upstream, client: 192.168.1.148, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "http://192.168.1.5/Plugins"

 

 

I saw other people having issues with this plugin recently as well, so I uninstalled it before making this thread, I'm unsure why it's still floating around in the logs.

But... that plugin also isn't running during the fresh copy version that I tested (as far as I know). I only had Unassigned Devices installed.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.