<?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>Msdm on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/msdm/</link>
    <description>Recent content in Msdm 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/msdm/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>
  </channel>
</rss>
