<tt><font size=2>> From: Stephen John Smoogen <smooge@gmail.com></font></tt>
<br><tt><font size=2>> > On Tue, Nov 13, 2012 at 08:00:23PM -0500,
Ben Cotton wrote:<br>
> > On EC2 (as in many virt environments) the hardware clock source
is actually<br>
> > synced and running an ntpd service on the client is redundant.<br>
> ><br>
> <br>
> <bikeshed=blue><br>
> They say it is .... but it is not always. I have had multiple
cases<br>
> in KVM and some in Xen where supposedly the clock is kept up but what<br>
> you end up is actually watching time go backwards if you hit heavy<br>
> load in IO or CPU or Mem. Of course if you run into hardware
like<br>
> that.. you can install it after your DB has gone poopsies.<br>
> </bikeshed><br>
</font></tt>
<br><font size=2 face="sans-serif">I've seen that happen as well. I
found this by hitting the pause button on the guest IIRC. I just
always use NTP to avoid the worry, but I agree NTP (whether ntpd or chronyd)
belongs in @standard not @core.</font>
<br><font size=2 face="sans-serif"><br>
--<br>
John Florian</font>
<br>