When engineers first hear about OpenShift Virtualization (formerly CNV / Container-Native Virtualization), their immediate reaction is often skepticism:
"Wait... are you putting an entire virtual machine inside a container? Isn't that anti-pattern virtualization-ception?"
The short answer: No.
OpenShift Virtualization does not run a hypervisor inside a container. Instead, it leverages the open-source KubeVirt technology to treat Virtual Machines as native Kubernetes workloads—giving VMs the same declarative deployment, GitOps pipelines, software-defined networking, and storage capabilities as regular containers.
In this first part of our series, we're popping the hood to see how KubeVirt actually coordinates compute, memory, and kernel primitives across an OpenShift cluster.
🏗️ The Big Picture Architecture
At its core, a virtual machine on Linux is simply a QEMU process running in user space, accelerated by the KVM kernel module.
KubeVirt encapsulates that QEMU process inside standard Linux…