I synchronized the host using chrony and nearby stratum 1's and then compared the PHC time to the host time. The results are bizarre. I have only oneVM, so this result might not hold elsewhere. Miroslav suggests this might be a hyper-v issue.
Hope this image gets through the mailing list. If not, I'll post it elsewhere. [image: image.png] On Wed, Feb 26, 2025 at 2:22 AM Miroslav Lichvar <mlich...@redhat.com> wrote: > On Wed, Feb 26, 2025 at 12:59:20PM +0800, Mingye Wang wrote: > > I can see why Microsoft Azure picked that option: they don't want to > > overload the NTP pool (like I've complained about recently)[1], but > > their approach is a bit off. Specifically, I believe they should have > > specified a nonzero stratum so that chrony does not place too much > > trust in the host time. Is there anyone from Azure that I can contact > > on this issue? > > If there is only one source, it doesn't matter what stratum it has. > Its weight can change only relative to other sources. > > If you want to propose changes to the default configuration, you will > need to find out where it is coming from. There could be a base image > provided by the OS vendor and other changes layered on top maintained > elsewhere. Not easy to follow. I think most of the Azure stuff is on > github. > > -- > Miroslav Lichvar > > > -- > To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org > with "unsubscribe" in the subject. > For help email chrony-users-requ...@chrony.tuxfamily.org > with "help" in the subject. > Trouble? Email listmas...@chrony.tuxfamily.org. > >
