If there is a subject that has many and i realy mean many posts, and with these posts many many readers its timekeeping in vmware. Especially when your Guest OS is of the linux platform. Also there are many suggestions on how to solve this problem. Too give you guys a quick glace of whats happening out there… Some of the suggestions you might encounter.
1. Cron the ntpd refresh command. (put the ntp renew in a task and execute it every second)
(Not realy an option with 100Servers+ and loads, loads of network traffic)
2. Recompile the kernel using the 100Hz frequency setting instead of the 1000 or 250hz setting.
(One I want to test before discarding it, he might have a point there)
3. Patch the kernel / NTPD using the latest versions.
(Should be a standard job and best practice, not an suggestion!)
4. Use a VMWare compatible compiled rpm to reinstall the kernel.
(Sounds much like option 2 i want to test first, ill go for the manual compile 🙂 )
5. dont even want to mention all these other options
(too silly but fun reading 🙂 )
With all respect to the guys searching and finding solutions stated above. There was indeed a time these solutions where the best to apply. But time has gone past, vmware introduced solutions using the VMWare tools (almost the same a the cron solution). And communities responded comitted to solve these problems for their most valued distro. The result is a setting in the kernel that is available for various kernels, and these settings can be found on the VMware site. Even though i commited myself to test these various options before implementing one or the other, the bootloader option looks the savest to suggest too the big audience. So here it is.
Oh always there are people to thank 🙂
• My uncle for paying way more attention then me 🙂 Marco Gralike
• Prutser for breaking open the kernel discussion, good article there.
• VMware for maintaining there KB so well 🙂
• You for taking the time to read this nonsense 🙂