KVM and QEMU (virtualization)

The SC//Reliant™ platform uses both QEMU and KVM to run virtual machines (VMs) for efficient and comprehensive virtualization on each node. KVM provides high-performance CPU and memory virtualization, while QEMU provides comprehensive hardware device emulation and VM management. Together they form a Type 1 hypervisor that supports QCOW2-based virtual machines.

How KVM and QEMU fit together

• KVM (Kernel-based Virtual Machine). A Linux kernel module that turns the host kernel into a Type 1 hypervisor, exposing hardware-assisted CPU and memory virtualization (Intel VT-x or AMD-V).
• QEMU. A user-space emulator that handles device emulation (virtual NICs, virtual disks, virtual graphics, USB and PCI passthrough) and the guest lifecycle. When backed by KVM, QEMU uses the kernel's virtualization extensions for performance.

Together, KVM and QEMU let the SC//Reliant platform run unmodified guest operating systems with near-native CPU and memory performance, alongside the platform's containerized workloads, on the same node.

What runs on KVM in the SC//Reliant platform

KVM is the runtime for the platform's VM-based workloads, including:

• Legacy POS application servers that need a full OS environment.
• Back-office VMs.
• Vendor appliances delivered as virtual machines.
• Kubernetes (KxS) deployments run as VMs under the platform's Type 1 hypervisor.

Related documentation

• Managing KVM virtual machines: operational procedures.
• Configuring KVM virtual machines: VM definitions and configuration.
• VM workflow: end-to-end lifecycle.
• Backing up and restoring VMs: backup, snapshot, and bare-metal recovery model.
• The CLI reference covers RVC KVM subcommands for VM lifecycle, snapshots, and backups.