<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Xosé Fernández</title><link>http://xosefernandez.com/writing/</link><description>Recent content in Writing on Xosé Fernández</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 21 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://xosefernandez.com/writing/index.xml" rel="self" type="application/rss+xml"/><item><title>Building disposable Proxmox VMs from mutable base VMs with ZFS</title><link>http://xosefernandez.com/writing/building-disposable-proxmox-vms/</link><pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate><guid>http://xosefernandez.com/writing/building-disposable-proxmox-vms/</guid><description>&lt;p>When I moved my lab from VMware Workstation to Proxmox VE, one of the first
things I missed was linked clones.&lt;/p>
&lt;p>In VMware Workstation, I could take a snapshot of a normal VM and create a linked
clone from it. The clone was available almost immediately and used very little
additional storage at first. It was ideal for disposable test and development
environments.&lt;/p>
&lt;p>Proxmox VE also supports linked clones, but their source must be a template. That
did not fit how I wanted to maintain my base machines. A template cannot be
started like a normal VM, so updating it requires a separate workflow.&lt;/p></description></item></channel></rss>