Hi all,
I happen to have run into the problem as per the subject. What happened
is this:

* I recently installed a fully clean R4.0 system, with default templates
and sys-* qubes (this means fedora 26)
* I upgraded the default template, after cloning it, to fedora 28
* This means that now I have a fedora-28 based sys-net
* The system fails to sync the time to NTP servers

What I debugged until now:
* in sys-net, the service systemd-timesyncd should start and update the
time - it's enabled by default
* it does not, because it fails to start due to some inaccessible
directory that is not detailed in the logs
* googling around I found that it looks like one of the usual
surprise-ridden features of systemd, namely DynamicUser, that seems to
have problems with FUSE mounts and the custom-namespace-based isolation
(https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdTimesyncdFailure?showcomments).
I'm thinking this issue is manifesting itself with some of the Qubes
infrastructure.

Does anybody have a recommended way of fixing this, that avoids just
waiting for the systemd guys to fix this? I don't like the idea of
editing systemd's "packaged" unit files, nor am I willing to go set
weird permission / mount options for qubes' directory mounts. What I'd
like to have is a way of having dom0's time set from a network (NTP)
source without necessarily having to successfully set the time in my
sys-net.

What I'm thinking of doing is having a separate clock vm, with a more
standard ntpd, but I'm not sure of the network "position" inside qubes -
will it be enough to give it "sys-net" as the network vm?

Thanks in advance for any guidance...

-- 
Alex

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/04fdedfe-9502-e89b-2827-e09f00d73901%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to