cabbage/rvbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record provisioned Windows test VM

Browse Source
This commit is contained in:
cabbage
2026-09-09 05:50:47 +00:00
parent 541f050802
commit 2abf0bf19b
4 changed files with 187 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/testing.md
+16 -6
View File
@@ -87,6 +87,16 @@ cleanup.
`test/coverage.toml` is the incremental requirement-to-test inventory. The
`make verify` lint stage checks unique stable IDs and verifies every implemented
test reference against source. A resettable Windows smoke VM is now available.
The authoritative fixture record is
[testing-vm.md](testing-vm.md): it lists the VM/host UUIDs, Windows build,
hardware and device profile, NAT and VRDE endpoints, snapshot UUIDs,
credential-file contract, and the required reset sequence. At the last check
the VM was powered off with `baseline-disk-first` selected. The guest address
`10.0.2.15` is DHCP state only; use SSH plus VirtualBox Guest Control rather
than treating it as a stable endpoint. VRDE is enabled at
`192.168.50.162:3389` for diagnostics, while native Windows RDP is disabled in
the baseline.
The exact headless VirtualBox/Guest Control adapter is
`scripts/windows/test-host.ps1`; it takes the VM name, baseline snapshot, and
guest identity/password-file only from host environment variables, acquires an
@@ -97,10 +107,10 @@ inline password. Use `Prepare`, `Run`,
`Collect`, `Stop`, and `Reset` in that order for a native run. The VM is the
minimum smoke lane, so deferred native multi-session/ambiguous-session, Server
Core, and older-build entries remain explicitly blocked until their own
fixtures exist. During the current Windows 10 fixture check, VirtualBox Guest
Control 7.2.16 rejected the GUI-subsystem `rvbox.exe` as a directly runnable
fixtures exist. A previous Windows 10 fixture probe found that VirtualBox Guest
Control 7.2.16 rejects the GUI-subsystem `rvbox.exe` as a directly runnable
guest executable; wrapping it through `cmd.exe` exited the RVBox process but
left the Guest Control wrapper waiting. The VM was restored and left powered
off, but native runtime coverage remains blocked until the host adapter gains a
GUI-process completion path (or a service-driven guest runner). Wine or a
protocol stub is not treated as equivalent coverage.
left the Guest Control wrapper waiting. This remains an adapter completion-path
limitation: native runtime coverage needs a service-driven or
console-compatible guest runner. Wine or a protocol stub is not treated as
equivalent coverage.