On Monday, 13 March 2017 15:02:42 UTC+11, Jean-Philippe Ouellet wrote: > On Sun, Mar 12, 2017 at 10:59 PM, Drew White <[email protected]> wrote: > > Question: Why does it not work properly then? > > Answer: Must be because of something you changed on your system. > > It *does* appear to work properly by default, confirmed by not seeing > the NTP traffic you describe on two Qubes machines, one of which is > literally a perfectly unmodified default install of 3.2 I have just > for testing things. > > > Thus, it kept running /usr/sbin/ntpdate pool.ntp.org > > > > Until I changed that, it was futile. > > Feel free to send patches to allow users to easily specify an ntp server(s). Well, at this time, it's easiest to change it in the templates, and let it be populated downwards. Until a better functionality is implemented, it's not going to be more useful.
If I myself provided applications/services to enable this, then that would take me a bit of time to achieve properly due to the fact that it would have to work in version 4 as well. > >> >> > The "ClockVM" does not seem to be operating the way I would have > >> >> > thought a "ClockVM" would. > >> >> > >> >> Only the ClockVM to uses NTP at all, and it sends the time back to > >> >> dom0. The rest of the VMs get their time set by dom0 via > >> >> qubes.SetDateTime service. > >> > > >> > So the ClockVM ONLY interacts with Dom0. Fair enough. Then it would be a > >> > good addition to allow it to update each Guest. > >> > >> No. That would be a bad design for several reasons. Dom0 already does > >> this periodically. This is better than what I assume you suggest > >> (ClockVM directly invoking qubes.setDateTime in each guest) because > >> the service invocations are implicitly rate-limited and contents > >> filtered by dom0. It is also not desired for the ClockVM VM to even > >> know which other VMs exist, let alone know which ones are running and > >> need their clock set. > > > > I was more thinking the ClockVM (CVM) gets the time, then Dom0 gets the > > time, then Dom0 updates everything, it would all be via Dom0, but the CVM > > gets the time initially, and if it has a difference in the NTP compared to > > the time set in the CVM it then proceeds to update each guests time without > > calling an external NTP server, and keeps it all inside the Guest regime. > > Exactly. > > From my quick reading of the source and observations of my systems, > that appears to be exactly how it is implemented right now. In other words, the way it is right now is in a form in which it is yet to be complete because they have not instantiated the way that it's meant to work? > Note also that this is not what you initially described in your first email. It is not what I initially described because I was making an enquiry not providing details on what I had to do to change it per guest and not on a global level in such a way to reduce the impact on the system and the NTP server and DNS server. I posted on the forums, not sent an email, but I understand that you may think so because it's a forum that has a mailing list on it available. -- 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 [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-users/2e4348d2-8d4d-41be-a56f-33fa2925454f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
