Hello Jeremy Admittedly, I don't know much about NTP other than it's purpose and some of its abilities.
Without wanting to hijack this thread, I'm curious - are all of your NTP clients, VMs themselves? If VMs are so bad at tracking time, then what good are they for any reason? If an NTP client on a VM is able to track time and keep it's guest OS in-sync, then why is an NTP server (in a VM) any less accurate? Has anyone got a study they can reference? Or...are your VMs part of a Windows AD domain? If so, you will probably want to let your servers get their time sync from the domain controllers, so as not to inflict Kerberos problems on yourself. Or... are you sharing time for physical servers? If you have physical servers, why not just install an NTP service onto one of them and be done with it? Mike On Mon, Apr 4, 2016 at 12:18 PM, Jeremy Charles <jchar...@epic.com> wrote: > I’m seeing all sort of documentation about how it’s not a great idea to > use a VM as an NTP server due to how sketchy time tracking is within a VM. > > > > My supervisor directed me to try it anyway. He feels that our existing > NTP servers are too old and need to be replaced, and he wants to replace > them with VMs rather than physical servers. > > > > I’m not seeing any difference in behavior between the two existing > physical NTP servers and the VM that I set up to test as an NTP server. > > > > Thoughts? > > > > == > > Jeremy Charles > > Epic’s Computer and Technology Services Division > > jchar...@epic.com > > 608-271-9000 > > > > _______________________________________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ > >
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
