Skip to content

virtualbox: VBoxVMI physical reads and RAM ranges - #302

Merged
Wenzel merged 1 commit into
devfrom
vbox/vboxvmi-read
Oct 12, 2026
Merged

Wenzel merged 1 commit into
devfrom
vbox/vboxvmi-read

Conversation

@Wenzel

@Wenzel Wenzel commented Oct 12, 2026

Copy link
Copy Markdown
Owner

Closes #282.

  • VBoxVMI driver reads physical memory through batched PHYS_READ requests (multiple ranges, per-page status via rs-vboxvmi); unreadable pages are reported in bytes_read without failing the call, and a readable prefix survives a later transport/protocol error.
  • Max physical address derived 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: default method follows compiled features; records/restores 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 dumpvmcore passes 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.

…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
Wenzel force-pushed the vbox/vboxvmi-read branch from a9ab8aa to f85c90a Compare October 12, 2026 06:51
@Wenzel
Wenzel merged commit 94598d4 into dev Oct 12, 2026
22 checks passed
@Wenzel Wenzel mentioned this pull request Oct 12, 2026
5 tasks
Wenzel added a commit that referenced this pull request Oct 31, 2026
virtualbox: VBoxVMI physical reads and RAM ranges
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant