Change r3745 contained fixes that might be appropriate, too.
-Eric
DAVE CUSHING wrote:
I hadn't done the clock=pit since moving to ESX3, I thought it had been
dealt with - I'll give that a try and see if it helps. Thanks for the
help!
On 1/19/2007 at 1:17 PM, in message
<[EMAIL PROTECTED]>, "Chet
Luther"
<[EMAIL PROTECTED]> wrote:
On 1/19/07, DAVE CUSHING <[EMAIL PROTECTED]> wrote:
As far as I know, the time is fine. It is set via NTP at boot, and
set
to synchronize with the base machine. I am running SuSE 10 on
VMWare
ESX 3 - my other boxes have accurate time. The strange thing is
that it
always seems to be about a 7 minute jump.
I am going to run some experiments to check the clock and see if
that
is the problem, thanks for the reminder to check the obvious first
:)
Hopefully it will be a simple timing issue.
Dave,
I just wanted to second Dennis' diagnosis. I had this same problem
with a CentOS guest running inside a Windows VMware host. The
solution
for me was to add clock=pit to the end of my grub kernel config,
uninstall NTP and use vmware-tool(s|box) to let VMware manage the
clock synchronization.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
