StevenD

Since I no longer have to compile a new VMWare Tools package for each release, I added a wildcard to the plugin so that it should work with any version newer than 6.12.x, as long as it uses the v6.x kernel. So if you update to a new version, please let me know if you have any issues. I'll remove the wildcard and go back to the individual releases if there are issues. This currently works fine with 6.12.0-rc1 and -rc2. I expect it to work with any additional -rc and -release when it comes out.

Updated for 6.11.0 Stable Release. Some things have changed with 6.11, so I had to do a workaround. In order for VMWare Tools to start, I had to add: ln -s /usr/lib64/libffi.so.7 /usr/lib64/libffi.so.6 This very well could have an unintended consequence, or could cause an issue with another plugin. I am going to see if I can find someone a little more knowledgeable than me to walk through my plugin and see if there is a way to make it work each time unRAID gets updated. That being said, the plugin does allow you to shutdown unRAID cleanly from within vCenter or ESXi, which is all I really care about.

I somehow missed this when you first posted. I recently built two new servers with H12SSL-NTs and Epyc 7443Ps. I'm VERY happy with them.

I do not have any dockers set up with their own IP. Nothing special on the ESXi side, except I pass through all of my hardware:

I've been running unRAID on ESXi for around 10 years now, so there are no inherent issues in doing that. That being said, I have never seen your issue. I just looked at my config, and I have bonding and bridging off. I assume thats required to run dockers on their own IP.

Updated for 6.10.0 Stable Release.

Updated for 6.10-rc4

Updated for 6.10-rc3

Obligatory, "the Pro license is cheaper than even a single hard drive. In fact, the unRAID license is the cheapest thing in my servers."

Had a bit of time today, and I managed to get open-vm-tools compiled for 6.10-rc2! I even had a bit of luck on my side, as I was actually able to get it working with the latest VMWare Tools (11.3.5) without the ioctl "errors" spamming the event log. @doron

Check your power supplies. If both are plugged into the backplane, they both have to have power.

No, sorry. I just don't have time right now.

Ive messed around with it and cant get it to properly compile. Unfortunately, I have no time to mess with it right now.

The SM 836TQ is a great chassis, and the only chassis that I use. You will want to get some SQ power supplies, if you care about noise. However, the X8DTH is ancient and inefficient. You would be better off finding a barebones chassis, and adding your own motherboard, or finding something more modern. As soon as prices and availability are better, Im dumping the rest of my X9s.

Yes, the mover does run overnight. Unfortunately, I cant disable it for a week. At the end of the day, it doesn't really bother me that the parity check basically takes a week. It was problem for a while, as I was having some crashing. I had to reboot everything to fix the crash, which of course, cancels the parity check. My RTX 4000 was overheating and disappearing from the bus. I have improved cooling and solved that issue.