<?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 Cozystack</title><link>https://deploy-preview-802--cozystack.netlify.app/topics/virtualization/</link><description>Recent content in Virtualization on Cozystack</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 12 Nov 2026 04:51:41 -0700</lastBuildDate><atom:link href="https://deploy-preview-802--cozystack.netlify.app/topics/virtualization/index.xml" rel="self" type="application/rss+xml"/><item><title>Running Cozystack on Three 8 GB Raspberry Pi 5 Boards</title><link>https://deploy-preview-802--cozystack.netlify.app/blog/2026/11/cozystack-on-raspberry-pi-5/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-802--cozystack.netlify.app/blog/2026/11/cozystack-on-raspberry-pi-5/</guid><description>&lt;p&gt;Three Raspberry Pi 5 boards on a desk, and on them a cluster that runs containers and virtual machines, with multi-tenancy, managed databases and everything else Cozystack provides.&lt;/p&gt;
&lt;p&gt;Why bother? Cozystack is usually installed on a rack of servers in a data center, so just trying the platform out means renting hardware or spinning up VMs in a cloud. Three Raspberry Pis cost about as much as a dinner out, fit in a backpack and run from a wall socket. You can learn on them, demo Cozystack at a conference, debug your own automation or keep a small cloud at home. And I was curious how far the platform can be squeezed and what breaks first.&lt;/p&gt;</description></item><item><title>Cozystack 1.7: ARM, Proxmox as a KubeVirt Alternative, and Automated VMware Migrations</title><link>https://deploy-preview-802--cozystack.netlify.app/blog/2026/11/cozystack-1-7-arm-proxmox-vmware-migrations/</link><pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-802--cozystack.netlify.app/blog/2026/11/cozystack-1-7-arm-proxmox-vmware-migrations/</guid><description>&lt;figure&gt;&lt;img src="https://deploy-preview-802--cozystack.netlify.app/blog/2026/11/cozystack-1-7-arm-proxmox-vmware-migrations/cozystack-1-7-banner.png"
			alt="Cozystack v1.7.0 release banner — arm64 builds, Proxmox as a KubeVirt alternative, automated VMware migrations" width="720"&gt;
&lt;/figure&gt;

&lt;p&gt;Cozystack v1.7.0 is now available. The release was published on October 29, 2026.&lt;/p&gt;
&lt;p&gt;This release removes several of the usual reasons teams give for putting off a move to the platform. It is aimed at those who already run Proxmox VE and want to keep it, those leaving VMware and wondering how to bring their virtual machines along, and those who cannot expose a database without encryption or back up anything other than PostgreSQL.&lt;/p&gt;</description></item><item><title>A community catalog brings Niklaus Wirth's Oberon machine to Cozystack as an installable app</title><link>https://deploy-preview-802--cozystack.netlify.app/blog/2026/09/oberon-risc5-machine-as-a-cozystack-catalog-app/</link><pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-802--cozystack.netlify.app/blog/2026/09/oberon-risc5-machine-as-a-cozystack-catalog-app/</guid><description>&lt;figure&gt;&lt;img src="https://deploy-preview-802--cozystack.netlify.app/blog/2026/09/oberon-risc5-machine-as-a-cozystack-catalog-app/oberon-cozystack-catalog.jpg"
			alt="The Paleocomputing section in the Cozystack application catalog" width="720"&gt;
&lt;/figure&gt;

&lt;p&gt;A community contributor has published a pluggable Cozystack catalog that does something Cozystack was never built to do: it runs Niklaus Wirth&amp;rsquo;s RISC5 processor — the tiny teaching CPU Wirth designed for the 2013 edition of Project Oberon — as an ordinary cloud VM. From a tenant&amp;rsquo;s point of view, the 1980s Oberon workstation installs like any other app in the catalog: a short form, or a single &lt;code&gt;OberonVM&lt;/code&gt; resource, and the machine boots on a VNC console next to the PostgreSQL and Kubernetes instances. The whole thing is open source under Apache 2.0; the QEMU processor model, like QEMU itself, is under the GPL.&lt;/p&gt;</description></item><item><title>Security Advisory — CVE-2026-53359 ("Januscape"): KVM Guest-to-Host Escape</title><link>https://deploy-preview-802--cozystack.netlify.app/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-802--cozystack.netlify.app/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/</guid><description>&lt;figure&gt;&lt;img src="https://deploy-preview-802--cozystack.netlify.app/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/cve-2026-53359-banner.png"
			alt="Security advisory banner — CVE-2026-53359 Januscape KVM guest-to-host escape" width="720"&gt;
&lt;/figure&gt;

&lt;p&gt;&lt;strong&gt;Severity:&lt;/strong&gt; High for clusters running virtualization. &lt;strong&gt;Status:&lt;/strong&gt; No fixed Talos release yet — mitigation required now.&lt;/p&gt;
&lt;h2 id="what-happened"&gt;What happened&lt;/h2&gt;
&lt;p&gt;On 2026-07-06 a Linux kernel vulnerability, &lt;strong&gt;CVE-2026-53359&lt;/strong&gt; (&amp;ldquo;Januscape&amp;rdquo;), was publicly disclosed together with a working exploit. It is a use-after-free in the KVM/x86 shadow MMU that lets a &lt;strong&gt;guest VM break out to its host&lt;/strong&gt; (the cluster node) or crash the node&amp;rsquo;s kernel. It affects both Intel and AMD CPUs and has been latent in the kernel since 2010.&lt;/p&gt;</description></item><item><title>Cozystack 1.3: Storage-Aware Scheduling, LINSTOR GUI, and VM Default Images</title><link>https://deploy-preview-802--cozystack.netlify.app/blog/2026/04/cozystack-1-3-storage-aware-scheduling-linstor-gui-and-vm-default-images/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-802--cozystack.netlify.app/blog/2026/04/cozystack-1-3-storage-aware-scheduling-linstor-gui-and-vm-default-images/</guid><description>&lt;figure&gt;&lt;img src="https://deploy-preview-802--cozystack.netlify.app/blog/2026/04/cozystack-1-3-storage-aware-scheduling-linstor-gui-and-vm-default-images/cozystack-v1.3.0.png"
			alt="Cozystack v1.3.0" width="720"&gt;
&lt;/figure&gt;

&lt;h3 id="cozystack-13-storage-aware-scheduling-linstor-gui-and-vm-default-images"&gt;Cozystack 1.3: Storage-Aware Scheduling, LINSTOR GUI, and VM Default Images&lt;/h3&gt;
&lt;p&gt;
&lt;a href="https://github.com/cozystack/cozystack/releases/tag/v1.3.0" target="_blank"&gt;Cozystack v1.3.0&lt;/a&gt; is now available. The release also rolls up every fix shipped in the v1.2.1 → v1.2.4 patch line.&lt;/p&gt;
&lt;p&gt;This cycle pushes the platform forward in five clear directions: smarter storage placement, a managed UI for LINSTOR, a built-in catalog of VM base images, deeper application-level observability, and a complete cross-namespace VM backup-restore experience.&lt;/p&gt;
&lt;h3 id="main-highlights"&gt;Main highlights&lt;/h3&gt;
&lt;h4 id="storage-aware-scheduling-via-the-linstor-extender"&gt;Storage-aware scheduling via the LINSTOR extender&lt;/h4&gt;
&lt;p&gt;The &lt;code&gt;cozystack-scheduler&lt;/code&gt; now consults a &lt;strong&gt;LINSTOR scheduler extender&lt;/strong&gt; when placing pods that declare both a &lt;code&gt;SchedulingClass&lt;/code&gt; and LINSTOR-backed PVCs. Pods are preferentially scheduled to nodes where their volume replicas already live, cutting cross-node replication traffic and lowering I/O latency for storage-heavy workloads — databases, object stores, VMs.&lt;/p&gt;</description></item></channel></rss>