<?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>Qemu on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/qemu/</link>
    <description>Recent content in Qemu on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Sun, 04 Oct 2026 10:30:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/qemu/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Moving an OEM Licence Into a Proxmox VM, and What Moves With It</title>
      <link>https://blogs.damiendye.uk/en/proxmox/moving-an-oem-licence-into-a-proxmox-vm/</link>
      <pubDate>Sun, 04 Oct 2026 10:30:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/moving-an-oem-licence-into-a-proxmox-vm/</guid>
      <description>How the OEM licence in a PC&amp;#39;s firmware, the ACPI MSDM table, gets into a Proxmox VM: reading it, validating it before QEMU fixes up a broken one, storing it root-only in pmxcfs, and Microsoft&amp;#39;s own terms on moving it, including one VM on the licensed machine and why volume licences never use it.</description>
    </item>
    <item>
      <title>Branding a Proxmox VM, and Keeping It Branded Through the Next Upgrade</title>
      <link>https://blogs.damiendye.uk/en/proxmox/branding-a-proxmox-vm/</link>
      <pubDate>Sun, 04 Oct 2026 10:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/branding-a-proxmox-vm/</guid>
      <description>Five places a stock Proxmox VM shows somebody else&amp;#39;s name, and how to replace each so apt cannot undo it: SMBIOS strings filled from the VM&amp;#39;s own config, the SeaBIOS splash, a rebuilt OVMF logo or an option ROM that leaves the firmware alone, and the web UI logo, all read from source.</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>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>
    <item>
      <title>Always Use Q35, Not i440fx — Why It Matters on Proxmox VE</title>
      <link>https://blogs.damiendye.uk/en/proxmox/q35-not-i440fx/</link>
      <pubDate>Fri, 07 Aug 2026 08:45:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/q35-not-i440fx/</guid>
      <description>The two QEMU virtual chipsets are not interchangeable. Q35 provides a proper PCIe topology that passthrough, modern Windows, and the wider KVM ecosystem all depend on.</description>
    </item>
  </channel>
</rss>
