Generated Oct 3, 2026, 12:35:03 AM
Short-term recovery without full reboot: allow systemd-timesyncd/chrony to step time by making NTP reachable. If service-blocking problems persist, temporarily stop time-sensitive services, run 'sudo timedatectl set-ntp false' then 'sudo ntpdate -u <ntp-server>' (or 'chronyc -a makestep' if using chrony) to force a step, then restart services. These commands are reversible.
Prefer chrony on virtualized guests: install and enable chrony which handles large time steps and suspend/resume better than systemd-timesyncd in many environments.
Enable paravirtualized clock synchronization: install/enable the guest agent or hypervisor-specific tools (qemu-guest-agent) so the host can notify guests on resume to resync the clock.
On the hypervisor, avoid long suspended states during maintenance or ensure host triggers guest clock update at resume (libvirt and qemu have options to sync time).
For scheduled tasks, write cron-based guards (check for large clock skew on startup) and for certificate checks add short startup retries if time errors are transient. Escalation: If host behavior cannot be changed or chrony does not resolve the issue, involve virtualization infrastructure admin or host vendor — changes to host resume behavior may be required.