Comments on: Time Synchronize on VM and ESX http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/ Sun, 14 Mar 2010 13:42:20 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Jason Willey http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/comment-page-1/#comment-22 Jason Willey Wed, 27 Aug 2008 08:23:30 +0000 http://malaysiavm.com/blog/?p=131#comment-22 I did a little more checking and I found out why it works for the versions of linux you mentioned, but not for the one we are running. It has to do with the Linux guest's 2.4 kernel sending 1/10 of the timer interupts that 2.6 does, The time slip comes from the guest OS trying to respond to not being able to keep up with the interrupts. Apparently they have corrected the problem in the 2.6.18 release of the linux kernel. So avoid the 2.6 kernels prior to 2.6.18 in your vmware environment if you can... I did a little more checking and I found out why it works for the versions of linux you mentioned, but not for the one we are running. It has to do with the Linux guest’s 2.4 kernel sending 1/10 of the timer interupts that 2.6 does, The time slip comes from the guest OS trying to respond to not being able to keep up with the interrupts. Apparently they have corrected the problem in the 2.6.18 release of the linux kernel.

So avoid the 2.6 kernels prior to 2.6.18 in your vmware environment if you can…

]]> By: KW http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/comment-page-1/#comment-21 KW Wed, 27 Aug 2008 03:59:26 +0000 http://malaysiavm.com/blog/?p=131#comment-21 sometimes we shouldn't believe too much on all the best practices. Practical experience is more important and more suitable to your environment sometimes we shouldn’t believe too much on all the best practices. Practical experience is more important and more suitable to your environment

]]> By: superman http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/comment-page-1/#comment-20 superman Wed, 27 Aug 2008 02:39:55 +0000 http://malaysiavm.com/blog/?p=131#comment-20 We used SLES9, SLES10 & RHEL3 We used SLES9, SLES10 & RHEL3

]]> By: Jason Willey http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/comment-page-1/#comment-18 Jason Willey Tue, 26 Aug 2008 21:56:53 +0000 http://malaysiavm.com/blog/?p=131#comment-18 Interesting, VMware told us NTP in guests under 3.02 -3.5 wouldn't work. Are you using Redhat 4u5? Interesting, VMware told us NTP in guests under 3.02 -3.5 wouldn’t work. Are you using Redhat 4u5?

]]> By: craig http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/comment-page-1/#comment-15 craig Tue, 26 Aug 2008 11:03:13 +0000 http://malaysiavm.com/blog/?p=131#comment-15 For the Linux VM, you should try to sync through the NTP server in your environment. We are doing that in our environment now and we had put in 2 different NTP server as primary and secondary For the Linux VM, you should try to sync through the NTP server in your environment. We are doing that in our environment now and we had put in 2 different NTP server as primary and secondary

]]> By: CM http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/comment-page-1/#comment-12 CM Tue, 26 Aug 2008 03:58:40 +0000 http://malaysiavm.com/blog/?p=131#comment-12 For VM running Windows, it is a best practice to sync time with ESX host via VMware tools as Windows Time Service does not work well in virtual environment. For VM running Windows, it is a best practice to sync time with ESX host via VMware tools as Windows Time Service does not work well in virtual environment.

]]> By: Jason Willey http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/comment-page-1/#comment-10 Jason Willey Tue, 26 Aug 2008 01:24:16 +0000 http://malaysiavm.com/blog/?p=131#comment-10 Our Windows machines are always in sync via AD as well, unfortunatly our Linux machines are not always so lucky, and we have had to implement the fixes found in this article : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1420 Our Windows machines are always in sync via AD as well, unfortunatly our Linux machines are not always so lucky, and we have had to implement the fixes found in this article :
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1420

]]>