gnif/porthole-guest-driver — explained in plain English
Analysis updated 2026-07-21 · repo last pushed 2019-11-12
Monitor a Windows virtual machine's internal state from the host for malware analysis.
Debug a guest Windows OS at a low level without running inspection software inside the VM.
Build security research tooling that inspects VM memory externally via QEMU.
Develop and test custom QEMU virtual device communication with Windows guests.
| gnif/porthole-guest-driver | douglascorrea/syscall-agent | libretro/fixnes | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | C | C | C |
| Last pushed | 2019-11-12 | — | 2026-04-20 |
| Maintenance | Dormant | — | Maintained |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 4/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires building a custom QEMU fork from the author's repository and installing an unsigned Windows driver, which needs test-signing mode or signature enforcement disabled.
This repo provides a Windows driver for a custom virtual device called "porthole," designed to work inside QEMU (software that lets you run virtual machines on your computer). The driver lets a Windows virtual machine communicate with this special virtual device so that the host system, the real computer running the VM, can peek inside and inspect what the guest operating system is doing. At a high level, the porthole device acts as a bridge between the virtual machine and the outside world. When you run a Windows VM in QEMU, the guest operating system needs a driver to know how to talk to any virtual hardware it encounters. This project is that driver, it tells Windows how to interact with the porthole device so that inspection or introspection data can flow out of the VM to whatever tool on the host is listening. This would be useful for developers or security researchers who need to monitor or analyze a Windows virtual machine from the outside. For example, if you're building malware analysis tooling or debugging a guest OS at a low level, being able to inspect the VM's internal state without software running inside the guest itself is valuable. The porthole device essentially gives you a window into the VM's memory and state from the host side. A few practical caveats: the porthole device itself is still under development and hasn't been officially merged into the main QEMU project yet. To actually use this driver, you'd need a custom build of QEMU from the author's own repository. There's also no signed driver build available, which means Windows will likely complain about security warnings when installing it, since it lacks the digital signature Microsoft normally requires for approved drivers. The project is open-source under the MIT license.
A Windows driver for a custom QEMU virtual device that lets the host computer inspect the memory and state of a running Windows virtual machine from the outside, useful for malware analysis and low-level debugging.
Mainly C. The stack also includes C, Windows Driver, QEMU.
Dormant — no commits in 2+ years (last push 2019-11-12).
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.