Xen paravirtual guest and device interfaces
Code that lets a Linux kernel run as a guest (or control domain) on top of the Xen hypervisor, providing the paravirtual plumbing for memory ballooning, event channels, the xenbus/xenstore control plane, and front-ends for virtual disks, networks, and consoles. Xen is widely used in cloud hosting, XenServer/Citrix deployments, and increasingly in embedded and automotive systems.
recommendation
It should stay because Xen is a still-shipping hypervisor with active upstream maintenance, including stable-tree patches landing as recently as 2026 and a Xen Project 4.20 release in 2025. Commercial XenServer 8.4 is sold as production-supported with XenServer 9 in preview, and the project is actively pushing into embedded and automotive use on ARMv8, x86-64, and RISC-V, so removal would break a large and current user base.
repository signals
sources
- lore.kernel.org
Recent 2026 stable-bound patch traffic touched Xen code paths ("Partial revert \"x86/xen: fix balloon target initialization for PVH dom0\"") with Xen maintainers in trailers, indicating ongoing upstream maintenance rather than abandonment.
- xenproject.org
Xen Project published a 2025 Xen 4.20 release announcement describing ongoing security, performance, and hardware-support work, showing the platform remains current.
- xenserver.com
XenServer markets XenServer 8.4 as production-supported and XenServer 9 as in public preview in 2026, showing active new commercial deployments of the Xen stack.
- xenproject.org
The Xen Project explicitly positions Xen for current embedded and automotive deployments across ARMv8, x86-64, and RISC-V, supporting continued non-legacy use.
codex reasoning notes (technical)
`drivers/xen` is real driver code, confirmed locally via `rg` showing multiple `module_init`/`MODULE_DESCRIPTION` entry points for Xen guest interfaces. Lore evidence came from `lore_activity(file=drivers/xen/balloon.c)` and yielded the cited 2026 Xen-related stable patch URL; the directory-level `lore_file_timeline(drivers/xen/)` returned no matches, likely because it wants file paths, so I relied on per-file lore plus the provided commit statistics. Deployment evidence came from `web.search_query` on Xen Project/XenServer pages. Net: this is an actively maintained virtualization-driver subsystem for a still-deployed hypervisor ecosystem, so removal/deprecation is not supported by the evidence.