qubes' suspend hooks aren't called after VM suspend/resume (so VM clock is out of sync)

[taradiddles]

Qubes OS version:

R4.0rc3

Affected TemplateVMs:

fedora-26 (default - qubes rpm)

---

Steps to reproduce the behavior:

Start VM
Check time in dom0 and VM
Suspend laptop
Resume laptop X seconds later
Check time in dom0 and VM

Expected behavior:

Time in VM and dom0 should be the same

Actual behavior:

Time in dom0 is OK, but time in VM is lagging by X seconds

General notes:

running qvm-sync-clock manually in the VM synchronizes the clock so it looks like Qubes' suspend hooks aren't called ; dropping an executable debug script in /etc/qubes/suspend-post.d/ shows that it's indeed not called upon resume.

I didn't see anything relevant to suspend/resume in dom0 /var/log/qubes/vm-name.log

I'll be happy to test whatever is needed to help debugging but I'm not familiar enough with qubes-rpc and how events/hooks are propagated...

---

Related issues:

[andrewdavidwong]

Is this related to (or possibly even a duplicate of) #3135?

[andrewdavidwong]

Is this related to (or possibly even a duplicate of) #3135?

[taradiddles]

I don't think those are related:

• #3135 is related to NetworkManager: the dispatch "implementation" works but qubes-nmhook doesn't filter NM's events (interface down, change of connectivity, interface up, ...) and ends up being executed a few times in a very short time span.
• the problem here seems to be specifc to qubes (rpc / suspend hooks).

Note that I don't have anything "custom" on this 4.0rc3 install: I use the default fedora-26 template (+ some additional rpms but they don't have anything to do with qubes), and I only imported my 3.2 backups. FWIW, the hardware is the same as yours - T450s.

[taradiddles]

I don't think those are related:

• #3135 is related to NetworkManager: the dispatch "implementation" works but qubes-nmhook doesn't filter NM's events (interface down, change of connectivity, interface up, ...) and ends up being executed a few times in a very short time span.
• the problem here seems to be specifc to qubes (rpc / suspend hooks).

Note that I don't have anything "custom" on this 4.0rc3 install: I use the default fedora-26 template (+ some additional rpms but they don't have anything to do with qubes), and I only imported my 3.2 backups. FWIW, the hardware is the same as yours - T450s.

[taradiddles]

I rebooted my laptop (without any new updates) and after a full night suspended I don't see any time lag in VMs today. That's odd; I'll try to investigate when/if the problem reappears. Meanwhile, any pointer on what to look at (logs, rpc commands, ...) is welcome.

[taradiddles]

I rebooted my laptop (without any new updates) and after a full night suspended I don't see any time lag in VMs today. That's odd; I'll try to investigate when/if the problem reappears. Meanwhile, any pointer on what to look at (logs, rpc commands, ...) is welcome.

[taradiddles]

Closing, everything works as expected now although I didn't change anything (no updates, no tweaks, ...).
Probably a transient issue or a difficult-to-reproduce bug.
Will reopen if it happens again.

[taradiddles]

Closing, everything works as expected now although I didn't change anything (no updates, no tweaks, ...).
Probably a transient issue or a difficult-to-reproduce bug.
Will reopen if it happens again.