On Mar 25, 2011, at 10:37, Chuck Swiger wrote:
Well, take a look at the peerstats-- especially offset and jitter-- and
ntpd's rv assessment of the offset, jitter, and stability of the kernel clock
it is adjusting. The worst-case peer jitter if a factor of 4 worse in the VM
(2.468 vs.
On Mar 25, 2011, at 10:41 AM, Ask Bjørn Hansen wrote:
Well, take a look at the peerstats-- especially offset and jitter-- and
ntpd's rv assessment of the offset, jitter, and stability of the kernel
clock it is adjusting. The worst-case peer jitter if a factor of 4 worse in
the VM (2.468
Running ntpd is not easier than setting Xen's independent_wallclock =
0, or VMware's vmx option tools.syncTime = true. As for best, well,
I've yet to see data where that happens:
Actually the latest best practices for VMWare specifically state:
Note: In all cases use NTP instead of VMware
As a side note, here is how ugly my pool.ntp.org chart looks
because of this time reset issue going on:
URL: http://www.pool.ntp.org/scores/128.177.28.170
On Thu, March 24, 2011 3:00 pm, Alby wrote:
What could be going on with my NTP session that is causing the
time to reset a
On Thu, Mar 24, 2011 at 03:00:59PM -0400, Alby wrote:
What could be going on with my NTP session that is causing the
time to reset a every every hour or more? I've rebooted my box,
The most obvious thing would be that your clock is crazy in some way. Is
this a virtual machine of some
On Mar 24, 2011, at 12:00 PM, Alby wrote:
What could be going on with my NTP session that is causing the
time to reset a every every hour or more? I've rebooted my box,
deleted the drift file. Ran ntpdate to another server and then
started ntpd, and still I keep getting these resets.
Well,
On Thu, Mar 24, 2011 at 03:38:32PM -0700, Chuck Swiger wrote:
1) Running ntpd in the Dom0/host ESX/host is very useful. Keeping good time
there means that good time will be available to all of the VMs/guests via
independent_wallclock = 0, vmx option tools.syncTime = true, etc.
This is no
On Mar 24, 2011, at 7:42 PM, Ryan Tucker wrote:
If you do run ntpd, everything is fine. It has no problems keeping
accurate time, and the PLL stats show no differences from real hardware.
It makes for perfectly capable pool servers, too.
Please show me some data, ie, ntpq -pcrv output.
On Mar 24, 2011, at 11:13 PM, Chuck Swiger wrote:
On Mar 24, 2011, at 7:42 PM, Ryan Tucker wrote:
If you do run ntpd, everything is fine. It has no problems keeping
accurate time, and the PLL stats show no differences from real hardware.
It makes for perfectly capable pool servers, too.
