<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Chrony on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/chrony/</link>
    <description>Recent content in Chrony on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Fri, 07 Aug 2026 13:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/chrony/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A VM&#39;s Clock Cannot Be Trusted — and the ptp_kvm Fix for QEMU/KVM</title>
      <link>https://blogs.damiendye.uk/en/proxmox/vm-time-ptp-kvm/</link>
      <pubDate>Fri, 07 Aug 2026 13:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/vm-time-ptp-kvm/</guid>
      <description>A virtual machine&amp;#39;s clock is built on an assumption virtualisation breaks: that the CPU keeps counting. Why guest time drifts on every hypervisor, what the skew actually breaks — Kerberos, TLS, Ceph, Windows — and how ptp_kvm fixes it properly on QEMU/KVM.</description>
    </item>
  </channel>
</rss>
