test(windows): normalize USB tablet input after baseline restore

This commit is contained in:
cabbage committed 2026-10-08 08:21:15 +00:00
1 parent 4f1ed41f9f
commit 6ccaaae3c7
2 files changed
+49

No files matched your search

+5
View File
@@ -393,6 +393,11 @@ case "$action" in
VBoxManage snapshot "$vm" restore "$snapshot" >/dev/null
step prepare-snapshot-restored
assert_identity
# Baselines may retain PS/2-only input. On this fixture VRDE mouse
# movement reached Windows, but PS/2 button clicks did not. Use an
# absolute USB tablet before boot; keep the keyboard unchanged.
VBoxManage modifyvm "$vm" --usb-ohci on --mouse usbtablet --vrde-property 'Client/DisableInput='
step prepare-virtual-input-configured
VBoxManage startvm "$vm" --type headless >/dev/null
step prepare-vm-started
wait_guest_additions
+44
View File
@@ -307,6 +307,7 @@ For quick recovery, use this decision table:
| Inspect everything | `test/rdp-access/rdp-access status` | Read-only VM, Compose, tunnel, and IPv6-forward state |
| Start or reconnect access | `test/rdp-access/rdp-access up --bind 0.0.0.0 --public-host x1.xcel.me` | Reuses healthy services; recreates only missing tunnel/forward |
| Browser says “Waiting for response”, or resolution remains from an old preset | `test/rdp-access/rdp-access status`; `test/rdp-access/rdp-access logs --tail=100`; `test/rdp-access/rdp-access repair`, then sign in again | Diagnoses tunnel/dual-stack issues; clears cached web logins and stale guacd workers without restarting the VM |
| Clock updates but keyboard/mouse cannot control Windows | Follow the input recovery procedure below; do not assume a frozen guest or restore a snapshot | Separates video, keyboard, and mouse health; preserves the current disk |
| Partial stack or changed endpoint | `test/rdp-access/rdp-access down`, then `test/rdp-access/rdp-access up --bind 0.0.0.0 --public-host x1.xcel.me` | Recreates the exact project with the new settings |
| Print the current URL | `test/rdp-access/rdp-access url` | Read-only URL from the saved session |
| Stop temporary access | `test/rdp-access/rdp-access down` | Stops gateway, IPv6 forward, SSH watchdog/tunnel; retains verifier/cert |
@@ -314,6 +315,49 @@ For quick recovery, use this decision table:
| Reclaim exact unused images too | `test/rdp-access/rdp-access clean --images` | Also removes owned Guacamole/nginx images; leaves shared Alpine intact |
| Return VM to clean baseline | `scripts/windows/test-host reset --run-id interactive-rdp` | Stops/ restores the exact leased VM snapshot and leaves it powered off |
### Live video but missing input
Video updates do not prove keyboard or mouse input is working. First close
other desktop tabs, run `rdp-access repair`, and sign in again. Verify a harmless
keyboard shortcut (Windows+R, then Escape) and an actual button click, not just
pointer movement. Do not run a second independent RDP probe while the browser
owns the fixture's single VRDE connection slot.
On this Windows 10 / VirtualBox 7.2.16 fixture, the PS/2 pointing device accepted
pointer movement but did not activate buttons through Guacamole. A normal
Windows restart did not repair that mouse path. Switching to a USB tablet with
an OHCI controller did: the same real Guacamole HTTP-tunnel keyboard shortcut
opened Run, and the mouse Cancel-button click closed it. This identifies a
failure in the PS/2 input path for this setup, not its exact underlying driver
bug. Guest Control, the updating clock, and `Get-PnpDevice` reporting `OK` had
all remained healthy during the failure.
`scripts/windows/test-host prepare` now configures the USB tablet and enables
VRDE input **after each snapshot restore, before boot**. The retained baseline
snapshots are unchanged. A manual restore followed by `VBoxManage startvm`
bypasses this normalization and may restore the old PS/2-only configuration.
Oracle documents the USB tablet's absolute-coordinate input in its
[pointing-device settings](https://docs.oracle.com/en/virtualization/virtualbox/7.2/user/working-with-vms.html).
To repair a currently running VM **without discarding its disk changes**, first
ask the desktop user to save work. Use Guest Control to request a normal
Windows shutdown, wait until this exact VM is `poweroff`, then run on Helium:
```sh
# Defaults shown; substitute the verified VM name for another fixture.
VBoxManage modifyvm rvbox-win10-test --usb-ohci on --mouse usbtablet \
--vrde-property 'Client/DisableInput='
VBoxManage startvm rvbox-win10-test --type headless
```
Check the VM UUID and lease owner before changing it. Do not force a poweroff
if normal shutdown is blocked by unsaved work. Repair the Guacamole connection
and sign in again if necessary. This preserves installed files, Python and its
machine PATH; it closes running applications. Do **not** use `test-host reset`
or `prepare` for state-preserving recovery: both restore a baseline and discard
current disk changes. `rdp-access repair` alone never changes the virtual input
hardware or restarts Windows.
The two scripts have a deliberate ownership boundary. `rdp-access` manages only
the temporary browser gateway, Guacamole/guacd containers, IPv6 forward, and
Helium SSH tunnel. `scripts/windows/test-host` manages the leased VM and its