Clock drift on Lima VMs

[Ranjandas]

Today, I noticed some of my Lima VM clocks are stuck in the past.

[ranjan@lima-murphy-srv-01 ~]$ curl -s http://worldtimeapi.org/api/timezone/Etc/UTC | jq .utc_datetime
"2024-07-27T03:34:33.184974+00:00"

[ranjan@lima-murphy-srv-01 ~]$ date
Thu Jul 25 06:51:35 PM UTC 2024

[ranjan@lima-murphy-srv-01 ~]$ sudo journalctl -xfu chronyd
Jul 25 16:48:28 lima-murphy-srv-01 chronyd[747]: Source 108.61.56.35 replaced with 27.124.125.251 (2.fedora.pool.ntp.org)
Jul 25 16:51:41 lima-murphy-srv-01 chronyd[747]: Selected source 27.124.125.251 (2.fedora.pool.ntp.org)
Jul 25 16:51:41 lima-murphy-srv-01 chronyd[747]: System clock wrong by 12110.925657 seconds
Jul 25 16:52:45 lima-murphy-srv-01 chronyd[747]: Can't synchronise: no selectable sources
Jul 25 17:44:29 lima-murphy-srv-01 chronyd[747]: Source 27.124.125.251 replaced with 2001:44b8:2100:3f00::7b:7 (2.fedora.pool.ntp.org)
Jul 25 17:53:50 lima-murphy-srv-01 chronyd[747]: Source 2403:580c:c505:0:6955:67d3:6229:88e7 replaced with 103.76.40.123 (2.fedora.pool.ntp.org)
Jul 25 17:57:43 lima-murphy-srv-01 chronyd[747]: Source 2620:8d:c000::f replaced with 2001:470:1f0e:3e0::2 (2.fedora.pool.ntp.org)
Jul 25 18:13:10 lima-murphy-srv-01 chronyd[747]: Selected source 103.76.40.123 (2.fedora.pool.ntp.org)
Jul 25 18:13:10 lima-murphy-srv-01 chronyd[747]: System clock wrong by 29856.896084 seconds
Jul 25 18:41:36 lima-murphy-srv-01 chronyd[747]: Source 2001:44b8:2100:3f00::7b:7 replaced with 2604:a880:400:d0::83:2002 (2.fedora.pool.ntp.org)

I had to restart chronyd to get it back in sync.

Jul 25 18:53:55 lima-murphy-srv-01 chronyd[2582]: Selected source 159.196.3.239 (2.fedora.pool.ntp.org)
Jul 25 18:53:55 lima-murphy-srv-01 chronyd[2582]: System clock wrong by 117768.841879 seconds <<<<<<<<<<< 32 Hours
Jul 27 03:36:43 lima-murphy-srv-01 chronyd[2582]: System clock was stepped by 117768.841879 seconds
Jul 27 03:36:43 lima-murphy-srv-01 chronyd[2582]: System clock TAI offset set to 37 seconds
Jul 27 03:36:45 lima-murphy-srv-01 chronyd[2582]: Selected source 14.202.65.230 (2.fedora.pool.ntp.org)

Can anything be done in Lima to avoid this situation? Can the Lima VM time be in sync with the host's? What is the best way forward in this scenario? I appreciate any help you can provide.

[afbjorklund]

The host would need to run some NTP server for that to work, but it is supposed to use the provided RTC

• How to make guest time host time? #2396

[Ranjandas]

Thank you @afbjorklund. I think, in my case, I will have to figure out why Chrony didn't sync the time, even with so much drift.