<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Virtualization on AiSlackin</title><link>https://aislackin.com/tags/virtualization/</link><description>Recent content in Virtualization on AiSlackin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aislackin.com/tags/virtualization/index.xml" rel="self" type="application/rss+xml"/><item><title>hermes-proxmox-multihost: one skill, N standalone Proxmox servers</title><link>https://aislackin.com/posts/2026-07-17-proxmox-multihost-control/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://aislackin.com/posts/2026-07-17-proxmox-multihost-control/</guid><description>&lt;p&gt;Most home-lab Proxmox tooling assumes one cluster. Reality for a lot of us is several &lt;em&gt;standalone&lt;/em&gt; servers, accumulated over the years, each with its own login, its own quirks, and no interest in joining anybody&amp;rsquo;s cluster. This skill — built on danielbitpro/hermes-proxmox-control, extended with a host registry and a multi-host helper — lets one Hermes Agent session manage all of them.&lt;/p&gt;&#10;&lt;p&gt;The part I&amp;rsquo;m proudest of is the failure model: &lt;code&gt;get_all()&lt;/code&gt; wraps each connection in its own try/except, so when pve3 is down for maintenance, listing VMs across the fleet returns results from pve1 and pve2 plus a clean error line for pve3 — not a crash. Secrets resolve through Bitwarden Secrets Manager by UUID at call time; the registry on disk maps hostnames to secret IDs and never stores a credential itself.&lt;/p&gt;</description></item></channel></rss>