Fix fixture mouse integration and capture clean USB-tablet baseline
This commit is contained in:
1 parent
6ccaaae3c7
commit
90d6b05f4d
10 files changed
+424
-43
No files matched your search
+4
-2
@@ -198,8 +198,10 @@ 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. The reset target is
|
||||
`baseline-clean-python-ready`, which includes all-users Python 3.13.16, pip and venv
|
||||
but no installed RVBox client. The guest address
|
||||
`baseline-clean-python-usb-ready`, which includes all-users Python 3.13.16 on
|
||||
machine PATH, pip and venv, plus standard USB-tablet input without the problematic
|
||||
`VBoxMouse` class filter, but no installed RVBox client. Preparation verifies
|
||||
that mouse path; recovery and rollback are documented with the RDP helper. 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 only on Helium loopback
|
||||
at `127.0.0.1:3389` for diagnostics, while native Windows RDP is disabled in
|
||||
|
||||
Reference in new issue
Block a user