<?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>Migration on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/migration/</link>
    <description>Recent content in Migration on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Wed, 26 Aug 2026 10:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/migration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VMware to Proxmox with Ansible — Build the Shells Before You Move a Byte</title>
      <link>https://blogs.damiendye.uk/en/ansible/vmware-to-proxmox-ansible/</link>
      <pubDate>Wed, 26 Aug 2026 10:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/ansible/vmware-to-proxmox-ansible/</guid>
      <description>Reading a vSphere estate with the dynamic inventory, mirroring its VLANs into Proxmox SDN, and rebuilding every VM as a diskless shell before a single disk moves. Why every VMware info module hides the one field the migration needs, why vlan_id is three different types, and why one NFS export mounted twice turns the cutover into a local read.</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>
  </channel>
</rss>
