Aerowinder

Is this no longer working on the 6.4 betas? My modules are coretemp and jc42. Available sensors will sometimes show up in the drop down box (not usually), but when I attempt to save the selections, they revert back to Not used.

I'm not sure of your network configuration, but try: sudo ifconfig -a - you should see your network adapters here. You're looking for ens0p1, probably. Or something like that. sudo nano /etc/network/interfaces - is your required interface listed in this file?

This one has happened to me before. Did you try disabling automatic sleep in the VM under windows control panel?

Final update (hopefully): I contacted support about this, they looked into it, but couldn't find anything conclusive. Makes me feel a little better! Anyhow, I switched all my Debian and CentOS VMs over to Ubuntu 17.04. I've spent about 10 hours in the various VM's shells, and I haven't had a single NMI since. Pretty sure some weirdness is happening between my processor (Skylake) and ancient kernel those two distros use.

Don't mean to keep bumping my thread, but I have some more information. Hopefully the information I've posted thus far will come in handy for someone down the road. I'm running unRAID on my R230 - bare metal. This problem has really been driving me crazy for the past few days. This morning, I rebooted the server and went into the BIOS config. I had the power mode set to "Custom". The settings I had selected were the same as "Performance per watt" except the CPU power was set to Efficient instead of Performance balanced. I recently updated the BIOS on that machine, so the settings have been moved around a little. I selected Performance per watt option for power and rebooted. I did that over 12 hours ago, and haven't had another NMI. I will do some further testing. Firstly, I'll let this current setup run for a couple days. If still no problems, I will attempt to recreate the issue by setting my server's power config to custom and testing again. Hopefully, the issue comes back. I will update this thread when I have more information.

I've learned two things over the weekend: 1) Disabling watchdog does not stop the prompts. It seemed to originally, but they have returned. I double checked the status of watchdog, it was still disabled - just as I had left it. 2) All of my Debian VMs are now doing this. Not just the one with PostgreSQL. I noticed my other two VMs doing it this morning. For now, I've re-enabled watchdog on all 3 Debian VMs, and I've removed package "open-vm-tools" +autoremove from all 3. It's a VMware VM tools package. It's habit for me to install it, coming from ESXi, but doesn't do anything on KVM.

Greetings, I've been an unRAID user for a couple months now. My use case for it is simple. It is a backup datastore for my main NAS (Syno), and it is also my hypervisor. At this time, I run 5 VMs, 2 of them Windows, 3 of them Debian (on my cache SSD). I'm using the default settings for all VMs, except that I use qcow2 instead of raw to make moving the vdisk files off the cache drive quicker. Windows VMs seem to work fine. Debian VMs seem to work fine. Except for one: my Confluence VM. On my Confluence VM, after some arbitrary amount of time has passed, I start receiving the NMI messages via SSH. The number varies (20, 21, 31, etc). These occur exactly every 30 seconds. NMI messages are usually due to a hardware problem. I don't have a hardware problem. I know this because I've spent the last two days testing it. It's not a physical hardware problem. I did discover what is causing these messages, though. Confluence is a jumbled up mess of Java and Apache. So I wanted to blame Confluence. But it isn't the problem, either. I didn't exonerate Confluence until I attempted to set up Confluence on a CentOS VM. Before you set up Confluence, you set up PostgreSQL. NMI errors started occurring after PostgreSQL install, but before Confluence install. I was able to replicate this on my Debian VM. These distros include old versions of PostgreSQL, so I installed version 9.6.2 from the official repo. Same thing happens. Don't think it's a PostgreSQL bug, but PostgreSQL is without a doubt causing the problem. I've tried every combination of VM settings imaginable (within unRAID) to remedy these errors, nothing helps. These NMI errors don't seem to cause anything bad to happen. They just making using SSH kind of a chore. Here is how you stop those messages on Debian (may work on CentOS, did not test): sudo sh -c "echo 'kernel.nmi_watchdog=0' >> /etc/sysctl.conf" Reboot. No more error messages. You can check the current status of watchdog by using: cat /proc/sys/kernel/nmi_watchdog Will return 0 after you reboot, and should from that point onward. I've seen other posts on this issue in this forum with no solution. I saw someone mention disabling watchdog, but didn't say how. This is only a workaround, but it's the best you can do, for now. I'm pretty certain this is a KVM bug. Any ideas from anyone who knows more about this stuff than I do?