Le 06/02/2021 à 13:58, D. J. Bernstein a écrit :
A few times now I've suspended and resumed a Qubes laptop and seen a Fedora VM with the time it had before the suspend, where I expected it to instead switch to the current time. The non-switch seems perfectly correlated with a line likeFeb 06 09:48:16 ... qubes.SuspendPostAll-dom0[...]: Invalid date received, aborting! appearing in the VM's log shortly after an expected line like Feb 06 09:48:15 ... qrexec-agent[...]: executed root:QUBESRPC qubes.SuspendPostAll dom0 pid ... but I haven't dug further into how the dom0-VM date communication is supposed to work. dom0 and Debian VMs switch to the current time as expected.
Do you think it's related to the #4835 issue [1] ? Note also the linked issues (#3489, #4939).
And, see the recent related discussion [2] on the forum. [1] https://github.com/QubesOS/qubes-issues/issues/4835 [2] https://qubes-os.discourse.group/t/suspend-dom0-clock-errors/2870 -- Ludovic -- 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/70ee4476-cf63-6890-5564-93cee5c61a44%40zyrianes.net.
