whonix-ws-16 Template fails to update due to timing issue

[Patrick]

I thought suspend/resume as well as long running Templates should be improved by modifying qvm-sync-clock for Qubes-Whonix. Started working on it:

initial version of qvm-sync-clock.anondist

qvm-sync-clock.anondist code simplification

Not in use yet. And was probably in vain. And probably low priority.

Because…

---

@marmarek

The Whonix template is ~half a minute in the past. If it’s close enough that the 5 minutes makes a difference (date -s +5min is enough to fix), then I can very well believe that 30s in the past may be problematic at times too. Something clearly is making Whonix’s clock be in the past, and I’d say we should avoid it at all regardless if that’s 30s or 5min.

Then if this “small” difference is causing some much issues… The reason for that is probably:

Boot Clock Randomization

If someone would like to try if that is the case, try the workaround of disabling boot clock randomization.

Related boot clock randomization development discussion:
Boot Clock Randomization - bootclockrandomization