---
title: "QEMU/KVM"
description: "1 posts about QEMU/KVM, summarised, each linking to the original."
---

# QEMU/KVM
> 1 posts about QEMU/KVM, summarised, each linking to the original.

## Articles

### [Why we chose KubeVirt for our VM sandboxes](https://yomu.fyi/post/why-we-chose-kubevirt-for-our-vm-sandboxes.md)
- Company: [Boxcompute](https://yomu.fyi/company/boxcompute.md)
- Author: boxy
- Published: Sep 15, 2026
- Type: Explainer

BoxCompute chose KubeVirt for its VM sandboxes because workloads need a real Linux machine with a guest kernel, systemd, and machine-level workflows that process-oriented environments do not fully provide. KubeVirt adds VM resource types and controllers to Kubernetes, while launcher Pods run QEMU/KVM and the guest on a worker. The arrangement keeps placement, lifecycle, permissions, storage, and cleanup within the Kubernetes model, avoiding a separate VM management platform, although resource accounting and readiness still require sandbox-specific work. The post stresses that full virtualization does not automatically provide security: the platform still needs deliberate controls for host access, guest traffic, credentials, persistence, and cleanup after failures.