VMWare suggests you do NOT run NTP on the guest OS, only the master. You do not need your own ntp server to run ntp. <br><br>If you go to the VMWare site and forums there are many discussions on clock scew. <br><br>The way VMware virtualzes the system plays total havoc on the clocks. They might count slow or really fast, or jump forward and backwards.
<br><br>Also your terminology is confusing 'dom0' is a XEN thing ' guest os' is a vmware thing. It is hard to tell which product you are using. <br><br>If you are using VMware and the clock is slow or jumping around refer to my first post. If you are XEN I can not help much.
<br><br><br><br><div><span class="gmail_quote">On 7/2/07, <b class="gmail_sendername">Maurizio Marini</b> <<a href="mailto:maurizio.marini@cost.it">maurizio.marini@cost.it</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon July 2 2007 11:56, Maurizio Marini wrote:<br>> Someone there has a very bare and simple /etc/ntp.conf to get 2 master<br>> servers time synced?<br>The distro configuration is ok, it is necessary to wait half an hour after
<br>ntpd restart on server, before trying to sync time from clients.<br> m.<br><br>--<br>Fedora-directory-users mailing list<br><a href="mailto:Fedora-directory-users@redhat.com">Fedora-directory-users@redhat.com</a>
<br><a href="https://www.redhat.com/mailman/listinfo/fedora-directory-users">https://www.redhat.com/mailman/listinfo/fedora-directory-users</a><br></blockquote></div><br>