Microsoft Hyper-V guest integration (VMBus and friends)
The guest-side plumbing that lets Linux run efficiently as a virtual machine on Microsoft's Hyper-V hypervisor, which powers Windows Server, Windows 11 VMs, and Azure. It includes VMBus, the channel carrying paravirtualized network, storage, and input traffic between the Linux guest and Windows host, plus memory ballooning and the newer MSHV/VTL interfaces.
recommendation
It should stay because Hyper-V is a current, heavily deployed Microsoft product and Linux guests on Windows Server 2025, Windows 11, and Azure rely on this code for usable network and storage performance. Upstream activity is healthy, with Microsoft engineers still landing new feature work in 2026, including additions for the MSHV/VTL stack. There is no in-kernel replacement and no sign of any retirement effort.
repository signals
sources
- lore.kernel.org
Upstream Linux Hyper-V/VMBus code is still receiving active feature work in 2026; this patch exports `vmbus_interrupt` for the `mshv_vtl` module and touches `drivers/hv/vmbus_drv.c`.
- lore.kernel.org
A 2026 v2 patch series is still restructuring shared Hyper-V/VMBus code, indicating active maintenance rather than retirement.
- learn.microsoft.com
Microsoft documents Hyper-V as a current virtualization platform for Windows Server 2025, Windows 11, and Azure Local, showing it remains a current product in new deployments.
- learn.microsoft.com
Microsoft's current guest-support documentation says Hyper-V supports Linux and FreeBSD VMs on Windows Server 2025/2022/2019/2016, Windows 11/10, and Azure Local, and recommends Hyper-V-specific devices for Linux guests.
codex reasoning notes (technical)
`drivers/hv` is the Microsoft Hyper-V guest driver stack (Kconfig says 'Microsoft Hyper-V guest support', including VMBus, utils, balloon, and newer MSHV/VTL pieces). I identified the family by local shell inspection of `drivers/hv/Kconfig` and module descriptions. Lore grounding: `lore_file_timeline` on `drivers/hv/vmbus_drv.c` showed heavy activity from 2021-2026 with newest touches on 2026-04-23; the cited lore URLs came directly from that MCP result. I attempted targeted removal/deprecation searches in lore (`lore_regex`, `lore_substr_subject`) plus `lei`, but regex/substring queries timed out and `lei` could not start in this sandbox, so I found no positive evidence of an upstream removal effort. Deployment evidence came from web search on Microsoft Learn pages showing Hyper-V is current in Windows Server 2025/Azure Local and that Linux guests are expected to use Hyper-V-specific devices. Because this is an actively maintained, currently deployed VM-guest interface with no natural in-kernel replacement, the correct hint is `keep`.