VBox 2a: Upstream patch: IMachineDebugger physical memory read/write #272

Parent

#269

What to build

Stock-VirtualBox SDK users can read and write guest physical memory through IMachineDebugger::readPhysicalMemory/writePhysicalMemory, which today return E_NOTIMPL. Built on the debugger memory API (DBGFR3MemRead/DBGFR3MemWrite); the missing entry points are added to the VMM function table by consuming reserved debugger-section slots (no version bump). On branch vmi/machinedebugger-memory, based on VirtualBox main, commits Signed-off-by.

Acceptance criteria

• Both methods work on a running and on a paused VM
• Unreadable/MMIO ranges return a clear error, never trigger device side effects
• A Python VirtualBox SDK script reads guest RAM and the bytes match a dumpvmcore core file of the paused VM
• The script writes a pattern, verifies it in a fresh core dump, and restores the original bytes
• No build flag or per-VM gate

Blocked by

• VBox 1b: Run VirtualBox on the host with a test guest #271