Repository navigation
libvmi: default VirtualBox access method #320
Description
Parent
What to build
With no access method init data, LibVMI asks libmicrovmi for the default (VBoxVMI at the default socket, else MachineDebugger). Explicit VBoxVMI without a socket path uses the VM's default socket. CI pin moves to the libmicrovmi dev commit that has the default and the vCPU count export.
Acceptance criteria
- No init data + VBoxVMI enabled → VBoxVMI used (libmicrovmi
infolog) - No init data + VBoxVMI disabled → MachineDebugger used
- Explicit VBoxVMI without path → default socket
- Explicit socket path that does not exist →
vmi_initfails - CI pinned to the new
devcommit and green
Activity
Wenzel commentedon Oct 21, 2026
Completed. The revived LibVMI libmicrovmi bridge, Ubuntu VirtualBox guest/profile, C vCPU-count export, default VBoxVMI selection and MachineDebugger fallback, explicit-access-method wiring, and the e2e harness are delivered. Evidence: libmicrovmi commits df0f1c7/2c2bcb8 and LibVMI commits baeb928/3ef30fe/1a56e01/850b4ff; the live VirtualBox e2e harness passed default, fallback, explicit VBoxVMI and MachineDebugger selections.