From 0104a73d1e170c1350fdc2d68cb7de7e19402815 Mon Sep 17 00:00:00 2001 From: Mathieu Tarral Date: Mon, 12 Oct 2026 12:30:56 +0000 Subject: [PATCH 1/2] docs: flag LibVMI mode vs access method ambiguity --- CONTEXT.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTEXT.md b/CONTEXT.md index cd2891ac..c635379e 100644 --- a/CONTEXT.md +++ b/CONTEXT.md @@ -42,3 +42,4 @@ Hypervisor-delivered notifications of guest activity (breakpoints, control-regis ## 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. From 11e27388cfdbc21aff3b1cc9878d213ad8f2b63e Mon Sep 17 00:00:00 2001 From: Mathieu Tarral Date: Mon, 12 Oct 2026 12:43:24 +0000 Subject: [PATCH 2/2] docs: glossary: default VirtualBox access method selection --- CONTEXT.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTEXT.md b/CONTEXT.md index c635379e..ade4c03e 100644 --- a/CONTEXT.md +++ b/CONTEXT.md @@ -38,6 +38,7 @@ 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