<?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>Ovmf on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/ovmf/</link>
    <description>Recent content in Ovmf on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Sun, 04 Oct 2026 10:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/ovmf/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
