ACRN Hypervisor Service VM Module
Intel's ACRN is an open-source Type-1 hypervisor aimed at industrial PCs, IoT gateways, and in-vehicle systems on modern Intel platforms. This kernel component is the Hypervisor Service Module that runs inside ACRN's privileged Service VM, letting Linux manage guest virtual machines, route I/O, and broker hypercalls on behalf of the hypervisor.
recommendation
Worth keeping but documenting its niche because ACRN is a specialized Intel hypervisor for industrial and IoT use, not a general-purpose virtualization stack. Intel still ships it for current platforms like Core i7-13700TE, Atom x6000RE, and Xeon D-1746TER through its Edge Controls for Industrial offering, and the code received treewide maintenance touches into 2025 with no replacement in sight, so removal would strand real deployments even though the audience is small.
repository signals
sources
- lore.kernel.org
Recent upstream touch to drivers/virt/acrn/hsm.c appeared in July 2025, indicating the code is still maintained.
- lore.kernel.org
drivers/virt/acrn/hsm.c was still being updated in March 2026 via a treewide x86 CPUID header cleanup, so the code is not abandoned in-tree.
- eci.intel.com
Intel ECI documentation describes ACRN as actively developed and aimed at IoT/embedded deployments, with a Service VM model matching this driver's role.
- eci.intel.com
Intel ECI 3.3 docs list current ACRN package support for boards using Intel Core i7-13700TE, Atom x6000RE, Xeon D-1746TER and related platforms, showing ongoing new-platform deployment in the 2025 timeframe.
codex reasoning notes (technical)
Real driver, not an internal helper: Kconfig and module_init show an ACRN Hypervisor Service Module for the privileged Service VM. `lore_file_timeline` on drivers/virt/acrn/hsm.c showed steady activity through 2025-03-27/2026-03-27 and no visible removal series in the sampled history; recent touches are mostly treewide/stable rather than feature growth, so this looks maintained but niche. Web search plus `open`/`find` on Intel ECI ACRN docs showed ACRN is still documented as actively developed and shipped for current industrial Intel platforms, so hardware/platform availability is still present in 2025. Deployment is likely low because ACRN is a specialized embedded/industrial hypervisor stack, and there is no natural upstream replacement driver for the same Service-VM interface, so keep the driver but annotate it as niche/platform-specific rather than deprecate or remove.