We are getting this on a few of our 64 bit 2 vCPU SQL 2005 servers. The article states that if there is a significant change in clock speed, this error can pop up. Would anything ESX does with clock cycles create this error - I assume it could.
The time stamp counter of CPU on scheduler id 2 is not synchronized with other CPUs
