<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Incus - vo.rs</title><link>https://vo.rs/tags/incus/</link><description>Latest from the Incus desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 09 Dec 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/incus/" rel="self" type="application/rss+xml"/><item><title>Incus: Containers and VMs Side by Side</title><link>https://vo.rs/story/incus-containers-and-vms-side-by-side/</link><description>&lt;p&gt;I spent a long weekend a few years back running two separate stacks on the same box: LXD for my system containers, and a hand-rolled libvirt setup for the two Windows VMs I kept around for testing. Two command sets, two networking models, two sets of storage pools to keep in sync. It worked, but every time I wanted to move a workload from a container to a VM — because it needed a real kernel, or GPU passthrough, or just more isolation — I was rewriting the whole deployment instead of flipping a flag.&lt;/p&gt;</description><pubDate>Tue, 09 Dec 2025 09:00:00 +0000</pubDate></item></channel></rss>