| Re: [chrony-users] Validating PHC operation on Microsoft VM |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Validating PHC operation on Microsoft VM
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 25 Feb 2025 08:48:37 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1740469724; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4eliVgsH7/vvduDNvTa1df0qy2VVIddD5DaQNLcgk+I=; b=JbQDJlpcAhTPj1WHcO4ofFuvq2UWK9jQNfdygE0Vq8wPNYGdd8yXxuRW40j8y/EEBXtjaR 8U+mjWI1mf78NVIXsQ+WFjkY0Aihb5u8cz/Rnj10Lbw79sAGkOonBHXc4aWAJSE35V/IhN zmLffIR8MFqIyGzCOS7tjSQdfdnk+J0=
On Mon, Feb 24, 2025 at 09:57:21PM -0600, Steven Sommars wrote:
> AFAICT chrony is happy, but is providing inaccurate time: Time is in error
> by 30-50 msec with substantial jitter.
>
> Dropping the PHC refclock and using nearby stratum 1's give much better
> results.
If you keep the refclock enabled with the nearby NTP sources, will it
be marked as a falseticker?
> Any suggestions for further debugging?
To me that sounds like the problem is in the synchronization of the
VM host's clock. An issue with the hyperv clocksource would impact
both PHC and NTP sources.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.