Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upFedora 28 VMs not updating time #3983
Comments
andrewdavidwong
added
bug
C: Fedora
labels
Jun 13, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
Jun 13, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
micah
Jul 3, 2018
This happens to me on every boot.
In order to fix it, I need to launch a terminal in sys-net and chmod 0700 /var/lib/private; systemctl start systemd-timesyncd.service and then go to dom0 and do sudo qvm-sync-clock in order for things to be right.
micah
commented
Jul 3, 2018
|
This happens to me on every boot. In order to fix it, I need to launch a terminal in sys-net and chmod 0700 /var/lib/private; systemctl start systemd-timesyncd.service and then go to dom0 and do sudo qvm-sync-clock in order for things to be right. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dmoerner commentedJun 12, 2018
Fedora 28 templates and Qubes 4.0.
qvm-sync-clock is updating dom0 to the wrong time because sys-net has the wrong time because systemd-timesyncd isn't starting with error status=238/STATE_DIRECTORY.
Fedora issue: https://bugzilla.redhat.com/show_bug.cgi?id=1559286.
Upstream report: systemd/systemd#7659
Manually changing /var/lib/private to 700, as mentioned in the above reports, fixed the problem for me. However, upstream commit systemd/systemd@ebe6ff6 which is merged in systemd in Fedora 28, which was supposed to fix this problem, seems not to have fixed it. Perhaps it needed to be combined with changing the permission on /var/lib/private in the Fedora package.