<?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>Kvm on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/kvm/</link>
    <description>Recent content in Kvm on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Wed, 12 Aug 2026 11:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/kvm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Creating Proxmox VMs with Ansible — The Host You Are Building Does Not Exist Yet</title>
      <link>https://blogs.damiendye.uk/en/ansible/proxmox-create-vms-community-proxmox/</link>
      <pubDate>Wed, 12 Aug 2026 11:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/ansible/proxmox-create-vms-community-proxmox/</guid>
      <description>The community.proxmox collection is an API client, not a configuration agent, and that changes the shape of every playbook. Where the tasks actually run, why proxmox_kvm declines to converge rather than update, why proxmox_disk and proxmox_nic own disk and NIC changes, and the undocumented return value you will end up needing.</description>
    </item>
    <item>
      <title>Proxmox VE Is Not a Hypervisor — KVM Is, and You Are Already Running It</title>
      <link>https://blogs.damiendye.uk/en/proxmox/kvm-the-hypervisor-inside-proxmox-ve/</link>
      <pubDate>Wed, 12 Aug 2026 09:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/kvm-the-hypervisor-inside-proxmox-ve/</guid>
      <description>&amp;#34;Is Proxmox enterprise grade?&amp;#34; is a question about the hypervisor, and Proxmox VE does not contain one. The hypervisor is KVM, the same kernel module under EC2, Google Cloud, Nutanix AHV and OpenShift Virtualisation. What Proxmox actually maintains, why the type 1 argument aims at the wrong line, and what the shared foundation does not buy you.</description>
    </item>
    <item>
      <title>Two Boot Lines — Which Kernel Flags Belong on a Proxmox Host, and Which Belong in the Guest</title>
      <link>https://blogs.damiendye.uk/en/proxmox/kernel-boot-flags-host-guest/</link>
      <pubDate>Fri, 07 Aug 2026 15:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/kernel-boot-flags-host-guest/</guid>
      <description>Most Proxmox tuning lines you find online are one blob of kernel flags. Half of them belong on the hypervisor, half belong inside the guest, two of the popular ones do nothing at all, and a few change meaning depending on which side of the boundary they land.</description>
    </item>
    <item>
      <title>A Virtual NVMe Device in Proxmox — and the Three Things You Give Up</title>
      <link>https://blogs.damiendye.uk/en/proxmox/virtual-nvme-proxmox/</link>
      <pubDate>Fri, 07 Aug 2026 14:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/virtual-nvme-proxmox/</guid>
      <description>QEMU can emulate a real NVMe controller, so the guest uses its own in-box NVMe driver with no VirtIO media required. It is also unmigratable by design, invisible to Proxmox backups, and no faster than VirtIO SCSI. Here is how to add one and when it is worth it.</description>
    </item>
    <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>
