Repository navigation
virtualbox: VBoxVMI physical reads and RAM ranges - #302
Merged
Merged
Conversation
…address from RAM ranges Physical reads go through batched PHYS_READ requests (several ranges per request, a status per page); unreadable pages are reported through bytes_read without failing the call, and the readable prefix survives a later transport or protocol error. The max physical address comes from RAM_RANGES. Python and C bindings can select the VBoxVMI access method. mem-dump derives the name from the socket and requires --no-pause for VBoxVMI; Volatility rejects vbox_socket_path unless method=vboxvmi. Test harness: the default method follows the compiled features, setup records and teardown restores VBoxInternal/VMI/Enabled, and the socket path is resolved like VirtualBox does (VBOX_USER_HOME, legacy ~/.VirtualBox, XDG_CONFIG_HOME rooted at $HOME when relative, ~/.config). The context is built with VirtualBox::new.
Wenzel
force-pushed
the
vbox/vboxvmi-read
branch
from
October 12, 2026 06:51
a9ab8aa to
f85c90a
Compare
Wenzel
added a commit
that referenced
this pull request
Oct 31, 2026
virtualbox: VBoxVMI physical reads and RAM ranges
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #282.
PHYS_READrequests (multiple ranges, per-page status via rs-vboxvmi); unreadable pages are reported inbytes_readwithout failing the call, and a readable prefix survives a later transport/protocol error.RAM_RANGES.mem-dumpderives the name from the socket and requires--no-pausefor VBoxVMI; Volatility rejectsvbox_socket_pathunlessmethod=vboxvmi.VBoxInternal/VMI/Enabled; resolves the socket path like VirtualBox (VBOX_USER_HOME, legacy~/.VirtualBox,XDG_CONFIG_HOME(relative → under$HOME),~/.config).Server side: Wenzel/virtualbox#4 (merged into
vmi/vboxvmi).Verified live: read-correctness vs
dumpvmcorepasses at 512 MiB and 5120 MiB (1536 MiB above 4 GiB); 1.9–2.8 GiB/s.cargo fmt --check,cargo clippy --features virtualbox-vmi --all-targets -D warnings, Python unit tests (16) pass.