There is no resolution for the issue at the moment.
Workaround:
Note:
Do not apply this setting on a machine that does not really have synchronized TSCs. If you do, the machine will eventually crash when the TSCs drift too far apart, and there may be confusing symptoms prior to the crash.
If the host definitely has synchronized TSCs, you can force the vmkernel to use the TSC as a global reference timer with the following boot option:
esxcli system settings kernel set --setting=timerForceTSC --value=TRUE
A reboot is required for the change to take effect.
Note: If this issue prevents the vmkernel from booting, you need to apply the workaround manually during boot in order to get the system to come up to the point where you can issue the
esxcli command shown above.
During the pre-boot splash screen, press Shift+O (the letter O) to modify the boot options. In the resulting screen, add the following to the end of the boot line:
timerForceTSC=TRUE.