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

docs: record Windows guest control GUI limitation

Browse Source
This commit is contained in:
cabbage
2026-09-06 14:47:05 +00:00
parent 0383155b86
commit 541f050802
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/testing.md
+7 -1
View File
@@ -97,4 +97,10 @@ inline password. Use `Prepare`, `Run`,
`Collect`, `Stop`, and `Reset` in that order for a native run. The VM is the `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 minimum smoke lane, so deferred native multi-session/ambiguous-session, Server
Core, and older-build entries remain explicitly blocked until their own Core, and older-build entries remain explicitly blocked until their own
fixtures exist. Wine or a protocol stub is not treated as equivalent coverage. 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
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.