If you are using VMware virtual servers, the recommendation is to use
the following two corrective measures:
1. Append clock=pit to your kernel boot line in grub.conf
2. In the vmx file for your virtual server, add the following line, or
modify it if it already exists as false:
tools.syncTime = "TRUE"
You can also configure this value through the VC console and you must
restart the virtual machine after making these changes for it to take
effect.
Then make sure you have the VMware tools installed, configured, and running.
ref: http://www.vmware.com/pdf/vmware_timekeeping.pdf
Thanks,
Josh Miller, RHCE
Scott Belnap wrote:
You can pass clock=pit to the kernel on boot up or use NTP.
On Sun, 2007-02-11 at 10:51 -0800, Scott Roberts wrote:
In rhel 4 and fc5 and fc6 the clock interrupt in the
kernel is 1000mhz. AFAIK this is too high and causes
the clock to drift and lose sync. This is even more of
a problem for virtual servers like vmware or zen.
Anyone experience this issue and have any workarounds
other than recompiling the kernel. Seems like a
drastic measure just to get an OS to keep accurate
time. I have looked for around for solutions and
thought maybe my fellow ldap admins might know something.
____________________________________________________________________________________
TV dinner still cooling? Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
