On Fri, Oct 27, 2017 at 7:10 AM, Marek Marczykowski-Górecki <[email protected]> wrote: > On Fri, Oct 27, 2017 at 01:01:13AM -0700, [email protected] wrote: >> I posted about my timezone problem in a previous message to which no one >> replied: https://groups.google.com/forum/#!topic/qubes-users/5guDJos5o3Y >> >> I'm assuming that since nobody replied, I am alone in having this problem >> which means that I have to research it myself. Could someone explain to me >> how the services work? I know that in the VM there is a file under >> /run/qubes-services that dictates whether or not the service is enabled. >> However, I would assume that there is some code somewhere that actually >> performs the clocksync activity, but I can't find any program or script >> that performs work. >> >> Can anyone explain how this works? > > Here is how it works: > > 1. sys-net runs some standard clock synchronization service (ntpd, > systemd-timesyncd - depending on template); it is enabled by setting > 'clocksync' service (qvm-service tool in dom0). > > 2. Then every VM, including dom0, synchronize its time directly from > there.
Although, it appears to not be *every* VM. Last I checked, Whonix VMs got their time indirectly through dom0 via qubes.GetRandomizedTime. A cursory examination of dom0's /etc/qubes-rpc/qubes.GetRandomizedTime and whonix's /usr/lib/sdwdate/clock-fix suggests that this is not your problem (both ends appear to use UTC), however I thought I'd mention it anyway for the sake of list-archive completeness. > In case of VMs, it is done by qvm-sync-clock (called from > qubes-time-sync.service in the VM), controlled by two things: > - absence (or disabling) of 'clocksync' service (qvm-service) > - qrexec policy, where actual VM used for time sync is set > (/etc/qubes-rpc/policy/qubes.GetDate) > For dom0, also qvm-sync-clock is used (slightly different one for dom0), > and the VM is set by 'clockvm' global setting (qubes-prefs). > > In theory, all those places should synchronize UTC time, and honour > local timezone for display purposes. But maybe somewhere it is messed > up... I'd start with checking timezone in sys-net and time > synchronization with the network (systemd-timesyncd.service) there. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CABQWM_Dyu90TywHMqUjrs-v4hEmHOx3J1iP0sG%3DLwciaWNiDXg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
