
The Multikernel Linux project has reached an important milestone with the release of mklinux 7.0-mk5, introducing native ARM64 support and expanding its experimental architecture beyond traditional x86-64 systems. Announced by developer Cong Wang on November 17, 2026, the release allows multiple independent Linux kernels to operate simultaneously on a single physical machine without relying on a conventional hypervisor. Each kernel receives its own allocation of processor cores, memory, and hardware devices, allowing it to execute directly on the underlying system.
The new release builds on Linux kernel 7.0 and introduces 114 additional patches compared with the previous mklinux 7.0-mk4 version. The complete development tree now contains approximately 330 patches beyond the upstream kernel. Although ARM64 compatibility is the most significant addition, the update also improves PCI device isolation, DMA protection, interrupt management, communication between kernel instances, and mechanisms for transferring control of a machine from one kernel to another.
Multikernel Linux remains an experimental project rather than a feature available in standard Linux distributions. However, its continued development demonstrates an alternative approach to operating-system architecture, particularly for environments where fault isolation, predictable performance, and recovery from kernel failures are important.
Understanding the Multikernel Linux Architecture
Most Linux systems operate under a single kernel responsible for managing every processor, memory region, hardware device, and running application. Even when a server executes hundreds of containers, those workloads generally share the same kernel and depend on its ability to coordinate resources safely. Virtual machines provide stronger separation by running individual guest kernels, but they require virtualization infrastructure to manage the relationship between the guest operating systems and the physical hardware.
Multikernel Linux approaches this problem differently. Instead of placing several operating systems inside virtual machines, it divides the physical machine into independent resource domains and assigns each domain to a separate Linux kernel. A host kernel initially controls the system, reserves a collection of processors and memory, and launches another kernel using those resources. Once started, the additional kernel operates directly on its assigned hardware, maintaining its own scheduler, memory management, and device drivers.
