Microsoft Hyper-V synthetic video DRM driver
The virtual display device that Microsoft's Hyper-V hypervisor exposes to Linux guests, providing the framebuffer and modesetting for VMs running on Windows Server, Windows 11, and Azure hosts. It is the modern DRM-based replacement for the older fbdev-style hyperv_fb driver and is the standard graphics path for Linux running inside Hyper-V.
recommendation
It should stay because Hyper-V is one of the major hypervisors Linux runs under in 2025, and this is the only in-tree driver for its synthetic graphics device. The code is actively maintained, with 2025 patch traffic adding drm_panic support, reworking the modesetting code, and landing build fixes, and Kconfig already directs users to prefer it over the legacy framebuffer driver.
repository signals
sources
- cateee.net
LKDDb identifies CONFIG_DRM_HYPERV as the Hyper-V synthetic video DRM driver, maps it to Microsoft PCI ID 1414:5353, and notes it is the DRM path preferred over FB_HYPERV in current kernels.
- mail-archive.com
Public patch traffic shows the driver still received a build-fix patch in November 2025, indicating active maintenance rather than abandonment.
- spinics.net
A 2025 drm-next patch series substantially reworked hyperv_drm modesetting/atomic helper code, showing ongoing upstream development.
- learn.microsoft.com
Microsoft still documents supported Linux guests on Hyper-V for Windows Server 2025, Windows 11, and related current platforms, so Hyper-V guest deployments remain current.
- static.lwn.net
Kernel documentation describes Hyper-V guest support as an active Linux virtualization environment across x86/x64 and arm64.
codex reasoning notes (technical)
Local tree inspection via shell `rg`/`sed` confirmed this directory is a real DRM driver for the Hyper-V synthetic video device and that Kconfig explicitly says to prefer it over FB_HYPERV. Local `git -c safe.directory=... log` showed recent 2024-2026 substantive maintenance, including replacing simple-KMS and adding drm_panic support. Web search against lore-related terms found no removal/deprecation hits; the obtained public patch pages from mail-archive and spinics instead show active 2025 maintenance. Deployment evidence came from Microsoft Learn and kernel Hyper-V docs obtained via web search, supporting continued real-world use in current Hyper-V Linux guest environments. Because this is virtual hardware tied to an actively shipped hypervisor, there is no natural upstream replacement driver beyond this driver itself.