On 2010-06-15, Krejci, Pavel wrote:
> Hi,
>
> since I cannot use kvm-clock as the clock source (older guest kernel) I am
> using pit as the clock source. According to my tests this is the most stable
> clock source among tsc,hpet but still can drift. Since the qemu keeps the
> /dev/rtc perfectl
On 2010-06-14, Marcelo Pimenta wrote:
> Hi everybody!!
>
> My question is about Time Accuracy of NTP/SNTP protocol. I want to know if
> is possible to have precision of 1ms(could be < 1 ms?) using SNTP in a
> network with 50 hosts(is the same with 100 hosts?) using only swithes, no
> routing. All
Hi,
So it seem that after a while NTP reject my GPS and PPS input for time
keeping. The only source for time sync is the GPS, I cannot use other
devices and/or remote servers.
I had to add support for my receiver (Trimble Resolution SMT) and
communication wise seems to communicate ok. The pp
Hi,
since I cannot use kvm-clock as the clock source (older guest kernel) I am
using pit as the clock source. According to my tests this is the most stable
clock source among tsc,hpet but still can drift. Since the qemu keeps the
/dev/rtc perfectly synchronized with the Host's system time it is
On Mon, Jun 14, 2010 at 3:03 PM, Marcelo Pimenta
wrote:
>
> Hi everybody!!
>
> My question is about Time Accuracy of NTP/SNTP protocol. I want to know if
> is possible to have precision of 1ms(could be < 1 ms?) using SNTP in a
> network with 50 hosts(is the same with 100 hosts?) using only swithes
Hi everybody!!
My question is about Time Accuracy of NTP/SNTP protocol. I want to know if
is possible to have precision of 1ms(could be < 1 ms?) using SNTP in a
network with 50 hosts(is the same with 100 hosts?) using only swithes, no
routing. All these hosts are syncronized with a Meinberg GPS. T
