<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Virtio on KINGsBlog</title><link>https://www.kanthi.in/tags/virtio/</link><description>Recent content in Virtio on KINGsBlog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 20 Nov 2026 10:20:00 +0530</lastBuildDate><atom:link href="https://www.kanthi.in/tags/virtio/index.xml" rel="self" type="application/rss+xml"/><item><title>MicroVMs with Firecracker on NixOS: From VT-x and KVM in Rust to Production VMMs</title><link>https://www.kanthi.in/posts/microvms-with-firecracker-nixos/</link><pubDate>Fri, 20 Nov 2026 10:20:00 +0530</pubDate><guid>https://www.kanthi.in/posts/microvms-with-firecracker-nixos/</guid><description>&lt;p&gt;Containers share a host kernel. Traditional virtual machines emulate a 1990s motherboard—BIOS, PCI bridges, IDE controllers, PS/2 keyboards, floppy drives—just to run a Linux server. &lt;strong&gt;MicroVMs&lt;/strong&gt; sit in the sweet spot between the two: hardware-enforced kernel isolation via KVM, paired with a minimalist, purpose-built Virtual Machine Monitor (VMM) that boots a Linux kernel in ~100 milliseconds with under 5 MiB of memory overhead.&lt;/p&gt;
&lt;p&gt;This guide builds the entire mental model from silicon up to production, using &lt;strong&gt;NixOS&lt;/strong&gt; as our reproducible host and guest platform. By the end, you will understand what the CPU actually does on a &lt;code&gt;VM-Exit&lt;/code&gt;, how to drive &lt;code&gt;/dev/kvm&lt;/code&gt; yourself in Rust, how a VMM boots Linux without a BIOS, how &lt;code&gt;virtio&lt;/code&gt; moves packets and disk blocks without burning CPU cycles, and how &lt;strong&gt;Firecracker&lt;/strong&gt;, &lt;strong&gt;Cloud Hypervisor&lt;/strong&gt;, and &lt;strong&gt;&lt;code&gt;microvm.nix&lt;/code&gt;&lt;/strong&gt; put it all together in production.&lt;/p&gt;</description></item></channel></rss>