The smartd service can leads to ESXi 6.0 or 6.5 hosts no responding due to out of memory. I see that issue on ESXi 6.0 U2 and U3 both. I would recommend stay on ESXi 5.5 U3 at this moment.
We do see the issue persist even after stop smartd service.
Check out VMware official KB.
Just noticed a issue that nothing reported in ‘Hardware Status‘ tab of ESXi hosts in vSphere Web Client. KB 2112847 gives a solution but not works for me. The feature can be used to monitor hardware failures. I figured out a way to workaround it. You just need to login by Administrator account and click ‘Update‘ button under ‘Monitor‘ – ‘Hardware Status‘ for each ESXi host. You will get the status after few minutes.
You may see following error when you scanning ESXi hosts by vCenter Update Manager.
Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and
firewall setup, and check esxupdate logs for details.
You also see similar logs in /var/log/esxupdate.log.
[Errno -2] Name or service not known
The root cause could be following:
- ESXi host cannot resolve DNS name of vCenter Update Manager Server.
- One of the DNS servers incorrect if you set multiple DNS servers on ESXi host.
用vSphere Web Client打开虚拟机的控制台时可以会遇到报错 “Unable to connect to MKS: Could not locate vmware-authd executable“。
You may get error “Unable to connect to MKS: Could not locate vmware-authd executable” when open virtual machine console in vSphere Web Client.
I just heared Transparent Page Sharing (TPS) is disabled by default in latest ESXi 5.5 patch. You may concern about that if your IT budget is tight since it means you need more memory for heavy virtual machines.