] orphan mode, manycast, and virtualization
unruh un...@invalid.ca wrote:
On 2013-09-09, Horvath Bob-BHORVAT1 bob.horv...@motorolasolutions.com
wrote:
Another question if you guys have the time :),
We situations in which we have almost everything deployed as virtualized
servers running
Horvath Bob-BHORVAT1 bob.horv...@motorolasolutions.com wrote:
Use A. C is horrible, and it is very easy for the VM's to exceed the
500PPM ntpd threshold. And ntpd does a really horrible job of
disciplining a clock that keeps changing and losing time on a short
timescale. It is designed for
Another question if you guys have the time :),
We situations in which we have almost everything deployed as virtualized
servers running inside of VMware ESXi.It seems like the recommendation on
time synchronization with ESXi has changed from release to release. It seems
to boil down to
On 2013-09-09, Horvath Bob-BHORVAT1 bob.horv...@motorolasolutions.com wrote:
Another question if you guys have the time :),
We situations in which we have almost everything deployed as virtualized
servers running inside of VMware ESXi.It seems like the recommendation on
time
To: questions@lists.ntp.org
Subject: [ntp:questions] orphan mode, manycast, and virtualization
Another question if you guys have the time :),
We situations in which we have almost everything deployed as virtualized
servers running inside of VMware ESXi.It seems like the recommendation on
time
unruh un...@invalid.ca wrote:
On 2013-09-09, Horvath Bob-BHORVAT1 bob.horv...@motorolasolutions.com wrote:
Another question if you guys have the time :),
We situations in which we have almost everything deployed as virtualized
servers running inside of VMware ESXi.It seems like the
Horvath Bob-BHORVAT1 wrote:
A) Run ntpd on the bare iron at the ESXi layer
and let it change the virtual hardware clock
(without ntpd running on VMs)
B) Run ntpd on the bare iron at the ESXi layer
and let ntpd on the VMs use it as a time source
C) Run ntpd on all the VMs and
