[qubes-users] Re: HVM standalone: no mouse after suspend-to-ram

[Stickstoff]

Dear group,

After I wake Qubes from suspend-to-ram, the mouse doesn't work in
Tails any more.

I did not, however, change anything in the Tails VM for it to now work.

Cheers,

Stickstoff




On 2024-02-01 13:40, Stickstoff wrote:

this issue resolved itself after reinstalling qubes r4.2 freshly, on another hardware. Maybe because it was a fresh install, maybe because it was directly r4.2 and not upgraded from earlier versions, maybe the difference is the different hardware.

Dear group,

I am having issues with the mouse not coming back after standby.


doesn't work in Tails any more. The mouse still works in Qubes OS and
other VMs. The (internal, non-usb) keyboard still works everywhere. I
do not have any other standalone VMs installed to compare. In Tails,
after waking up I only see two errors:

I am running Qubes 4.1.2 (R4.1), kernel 5.15.52-1.fc32.qubes.x86_64 The VM is a HVM standalone, running Tails OS, kernel 6.1.0-13-amd64 (Debian 6.1.55-1). After I wake Qubes from suspend-to-ram, the mouse

clocksource: timekeeping watchdog on CPU3: Marking clocksource
'tsc' as unstable because the skew is too large

and

usb 1-1: Failed to suspend device, error -110

where usb 1-1 seems to be the "QEMU USB Tablet" virtual mouse. Reading up, "error -110" seems to be some kind of timeout error.

Any ideas on this one? Is it even Qubes or XEN or qemu related, or
rather on the Tails side?



Thank you,

Stickstoff

(Yes, Tails doesn't like to be in VMs. Yes, this comes with its own security implications.)

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ffa2654d-8c5e-4518-9b67-d29c67a9a689%40posteo.de.

OpenPGP_signature.asc
Description: OpenPGP digital signature