On Fri, Apr 11, 2025 at 10:40:23PM +0000, Emmanuel Dreyfus wrote: > After one week of testing, one domU was never able to get ntpq -c kerninfo > reporting sync, but the local clock did not drift from the NTP server. > Two other domU were able to quickly sync and to keep it as is. The three > domU are on three different dom0 with the same hardware.
One o two sane domU was hit by the bug ater 6.5 days of uptime. offset to NTP server is -5s. # ntpq -c kerninfo associd=0 status=c613 leap_alarm, sync_ntp, 1 event, spike_detect, pll offset: 0 pll frequency: -114.557 maximum error: 2963.13 estimated error: 0.002 kernel status: pll nano mode=fll pll time constant: 10 precision: 1e-06 frequency tolerance: 495.911 pps frequency: 0 pps stability: 0 pps jitter: 0 calibration interval 0 calibration cycles: 0 jitter exceeded: 0 stability exceeded: 0 calibration errors: 0 -- Emmanuel Dreyfus m...@netbsd.org
