Esxi ntp not updating
Note The driver installation may add the /usepmtimer switch in the file.Once this (/usepmtimer switch) was done the clock was dead on time. I originally noticed this because VMware gave me a helpful tip on my laptop, but this page mentions the same thing: Quote from : VMWare tips and tricks Power saving (Speed Step, C-states, P-States,...) Your power saving settings may interfere significantly with vmware's performance. CPU frequency This should not lead to performance degradation, outside of having the obvious lower performance when running the CPU at a lower frequency (either manually of via governors like "ondemand" or "conservative").Other available timers include the PM_Timer and the High Precision Event Timer (HPET).Resolution: To resolve this problem check with the hardware vendor to see if a new driver/firmware update is available to fix the issue.In my case we are running VMWare Server 2.02 on Windows Server 2003 R2 Standard. I had the VMware Tools installed and set to sync the time.I did everything imaginable that I found on various internet sites.So I moved on to the configuration wizard and validated the details with no errors. So at this point my colleague @Jörn Rusch joined me to test all network settings done during the implementation and helped making sure the provided NTP servers are working as expected.We did take a closer look at the used commands and queried the NTP services directly.
There a several ways to do this from outside the VM, but I wanted to find a way to enable time sync from within the guest itself either on or after tools install.
Exactly this issue is described at the VMware KB1035833 which states that a NTP service running on a Microsoft Windows Server with default configuration may not response with a correct time for VMware services.
ESXi/ESX support synchronization of time with an external NTPv3 or NTPv4 server compliant with RFC 5905 and RFC 1305.
Also generating the new DNS records for forward and revers lookup queries.
I also test this step twice to make sure it is working. Shortly afterwards it stopped with an error during the first boot configuration of the VMware Platform Service Controller. ), checked the time on the nodes using “esxcli hardware clock get” and “esxcli system time get” which both showed the local time. I dig like a fanatic through the Vx Rail Manager installation log looking for a clou. 2018-01-01 ,000 – DEBUG – Running: ntpq -p 192.168.1.1 2018-01-01 ,000 – DEBUG – Output of command ntpq -p 192.168.1.1: 192.168.1.1: timed out, nothing received ***Request timed out 2018-01-01 ,000 – DEBUG – Output of command ntpq -p 192.168.1.2: 192.168.1.2: timed out, nothing received ***Request timed out It looks like, even though I added not one but two NTP servers during the validation, it did not work out.