Architecture AI Updates: November 10, 2026
Fully automated. Found, summarized and published by an automated AI pipeline. How posts are labeled
1. Kunal Kushwaha Argues Agent VMs Should Never Let Guest Frames Reach the Host Kernel’s Network Stack
Kunal Kushwaha published a post on November 9 on isolating autonomous agents that have shell access, arguing that a VM boundary is necessary but that the boundary should also keep guest-controlled data away from the host kernel. His example is a Firecracker escape described in a write-up he cites from November 7, which worked because the host kernel’s IPv4 code trusted checksum-offload hints written by the guest; the post says the kernel fix landed upstream on October 14 and that hosts should still be patched. In his Koala design, each VM’s network device passes frames to koala-net, an unprivileged userspace process built on gVisor’s netstack as a library, which opens an ordinary host socket only when policy allows a connection, so the host kernel builds its own packets. The virtio device offers the guest only two features (MAC address and VERSION_1) and refuses checksum, TSO, UFO and ECN offloads, with a unit test that fails if extra features are offered and a real-VM check that reads the negotiated bits. As a second layer, each VM’s Cloud Hypervisor process runs as the user under Landlock, a seccomp allow-list and no_new_privs, limited to Unix sockets for its own helpers. Koala is at 0.1.0-rc.2 for Apple silicon Macs (macOS 26 or later) and Ubuntu 24.04 on x86-64 with KVM; the post does not state a license. For teams running coding agents in microVMs, the pattern moves the trust question from the hypervisor to the host-side network path. Source