Affected versions: CentOS Stream 10

📖 ~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

chrony drifts on virtualized guests on CentOS Stream 10 disrupts services and slows incident response until the root cause is resolved.

Environment & Reproduction

Time drift exceeds 100 ms on KVM guests because hypervisor clocksource is unstable.

chronyc tracking
chronyc sources
cat /sys/devices/system/clocksource/clocksource0/current_clocksource

Root Cause Analysis

Misalignment between time configuration and CentOS Stream 10 defaults causes the failure path described above.

Quick Triage

Confirm package state, service status, and recent changes before deeper diagnostics.

systemctl status
rpm -qa | grep -i 
journalctl -p err -b --no-pager | tail -100

Step-by-Step Diagnosis

Capture detailed logs, configuration deltas, and runtime state to isolate the failing component.

chronyc -n sources -v
journalctl -u chronyd -n 200
ntpstat
Illustrative mockup for centos-stream-10 — time_chrony_diagnostics
Diagnostics for time/chrony on CentOS Stream 10 — Illustrative mockup — Progressive Robot

Solution – Primary Fix

Apply the targeted configuration change and restart the relevant services to restore expected behavior.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

echo 'kvm-clock' | sudo tee /sys/devices/system/clocksource/clocksource0/current_clocksource
sudo chronyc -a makestep
sudo systemctl restart chronyd
Illustrative mockup for centos-stream-10 — time_chrony_fix_results
Fix verification for time/chrony on CentOS Stream 10 — Illustrative mockup — Progressive Robot

Solution – Alternative Approaches

Switch to a dedicated chrony hardware peer when virtual clocksources are unreliable.

Verification & Acceptance Criteria

Validate the fix with deterministic checks and ensure no regressions in dependent services.

chronyc tracking
timedatectl

Rollback Plan

Revert configuration and restart services to return to the previous known-good state.

cp /etc/chrony.conf.bak /etc/chrony.conf
systemctl restart chronyd

Prevention & Hardening

Pin clocksource via kernel boot parameter and monitor chrony tracking.

Related: kvm-clock, makestep, jitter; see also adjacent topics in the CentOS Stream 10 common problems series.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

CentOS Stream documentation, Red Hat upstream guides, and CentOS Stream 10 release notes covering this subsystem.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.