virtio-mem goes to Windows
summary
virtio-mem for Windows aims to add and remove RAM ranges dynamically by implementing a Windows driver; work requires heavy reverse engineering because official docs hide MmAddPhysicalMemory and MmRemovePhysicalMemory usage. Analysis of pnpmem and mvc.sys shows add uses MmAddPhysicalMemory while hot-remove relies on an undocumented MmAllocatePagesForMdlEx flag. Hyper‑V requires an undocumented hypercall (HV call 0xBC) plus enabling Hyper‑V enlightenments and partition privilege flags to succeed; NUMA, hibernate and tooling edge cases remain.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:29Agenda
- 1:37Concept
- 3:10Presentation
- 3:53Challenges
- 4:48What is really needed
- 6:21Drivers
- 9:00Memory drivers
- 13:30HyperV
- 16:25Other challenges
- 17:12Additional information
- 18:15Outro
related talks
34mVirtio-msg: Making Virtio Work Where It Does Not Today
36mShared Virtual Addressing for High Performance Arm Infrastructure Platforms
28mXen VPCI Weather Report
30mEnabling a Software-Defined Automotive Edge with VirtIO Based Device Virtua...
18mZVM: Zephyr-based Virtual Machine
35mZephyr OS Memory Protection
35mVirtio-Loopback: An Hardware Abstraction Layer (HAL) for Non-Virtualized Environm...
32mDeveloping the RISC-V Hypervisor Extensions in QEMU