Skip to content

docs: flag LibVMI mode vs access method ambiguity #311

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Wenzel merged 2 commits into from
Oct 17, 2026
Merged

docs: flag LibVMI mode vs access method ambiguity #311

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0104a73
docs: flag LibVMI mode vs access method ambiguity
Wenzel Oct 12, 2026
11e2738
docs: glossary: default VirtualBox access method selection
Wenzel Oct 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CONTEXT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,9 @@ Hypervisor-delivered notifications of guest activity (breakpoints, control-regis
- Both methods provide **VM state access**; only the **VBoxVMI method** is planned to provide **VMI events**
- Pausing through either method is the ordinary VirtualBox pause, visible to (and undoable by) the VM's user
- A **VBoxVMI** client that disconnects leaves no trace: intercepts are removed and anything it paused is resumed
- When the caller selects no **Access method**, the VirtualBox **Driver** uses the **VBoxVMI method** if the VM serves a VBoxVMI socket, and the **MachineDebugger method** only if it does not; an explicitly selected method never falls back

## Flagged ambiguities

- "VirtualBox driver" was used for both the libmicrovmi Driver and the patched hypervisor — resolved: **Driver** is always the libmicrovmi side; the hypervisor side is "patched VirtualBox".
- "Mode" in LibVMI (Xen, KVM, VirtualBox, ...) names the hypervisor being monitored — resolved: a **LibVMI mode** corresponds to a libmicrovmi **Driver**, never to an **Access method**; VBoxVMI and MachineDebugger are two access methods of one LibVMI mode.
Loading