Time Drift in VM Despite NTP Enabled

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

System time drifts, breaking TLS validation, scheduled jobs, and distributed log correlation.

Environment & Reproduction

Ubuntu 20.04 guests on hypervisors with suspend/resume events or host clock instability.

Root Cause Analysis

Guest time source conflicts with host sync policy or NTP service has poor upstream quality.

Quick Triage

Compare guest-host time, check synchronization state, and inspect recent time adjustments.

Step-by-Step Diagnosis

Validate `timedatectl`/`chrony` metrics and confirm virtualization clocksource behavior.

Solution – Primary Fix

Choose a single sync authority, tune NTP settings, and apply recommended hypervisor guest tools.

Solution – Alternative Approaches

Pin to trusted internal NTP servers and disable conflicting host-guest sync mechanisms.

Verification & Acceptance Criteria

Clock offset remains within defined tolerance over sustained workload and reboot tests.

Rollback Plan

Revert time daemon changes if application timing assumptions are disrupted.

Prevention & Hardening

Monitor NTP offset continuously and standardize guest clock configuration in templates.

Related Errors & Cross-Refs

Certificate not yet valid/expired errors and Kerberos authentication failures from skew.

Related tutorial: View the step-by-step tutorial for Ubuntu 20.04 LTS.

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu time synchronization docs and hypervisor-specific guest timing recommendations.