ntp (in a netvm) sudenly fails... (happend more than once)

[joanna]

[user@netvm user]$ sudo cat /var/log/messages | grep ntp | grep systemd
Jan 29 00:53:05 netvm systemd[1]: ntpd.service: main process exited, code=exited, status=255
Jan 29 00:53:05 netvm systemd[1]: Unit ntpd.service entered failed state.
[user@netvm user]$ 

This results in all clocks in my system getting hugely desynced, by an offset of several hours (which is strange, BTW, because ntp crashed only last night, and this morning my clocks went crazy...)

[joanna]

Maybe we should exclude the "clock VM" from being updated by Dom0 upon resume, as it might be causing the ntpd failure?

[marmarek]

I think yes - clock VM is the _source_ of time for dom0 (and in result other VMs).

[joanna]

Most likely fixed by this:

​http://git.qubes-os.org/?p=joanna/core.git;a=commitdiff;h=ddecfab7e81df49d0ff1facf2eedd26713da522chttp://git.qubes-os.org/?p=joanna/core.git;a=commitdiff;h=ddecfab7e81df49d0ff1facf2eedd26713da522c