<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Linux VM time sync</title>
    <link>http://communities.vmware.com/community/vmtn/general/vm-guest?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 14 Apr 2009 19:16:24 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-04-14T19:16:24Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Linux VM time sync</title>
      <link>http://communities.vmware.com/message/1225407?tstart=0#1225407</link>
      <description>In my environment all the Windows VMs were set to sync to DC before I took over. Since they don't have any problems, I just leave it alone.</description>
      <pubDate>Tue, 14 Apr 2009 19:16:24 GMT</pubDate>
      <author>Byron_Zhao</author>
      <guid>http://communities.vmware.com/message/1225407?tstart=0#1225407</guid>
      <dc:date>2009-04-14T19:16:24Z</dc:date>
      <clearspace:dateToText>7 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Linux VM time sync</title>
      <link>http://communities.vmware.com/message/1225122?tstart=0#1225122</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
 I post earlier same question...&lt;br /&gt;
&lt;p /&gt;
But why Vmware decides suddenly to change time sync's recomandations ? and it's ok for the windows guest too?&lt;br /&gt;
&lt;p /&gt;
Regards,</description>
      <pubDate>Tue, 14 Apr 2009 14:35:47 GMT</pubDate>
      <author>Boudeboi</author>
      <guid>http://communities.vmware.com/message/1225122?tstart=0#1225122</guid>
      <dc:date>2009-04-14T14:35:47Z</dc:date>
      <clearspace:dateToText>7 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Linux VM time sync</title>
      <link>http://communities.vmware.com/message/1225004?tstart=0#1225004</link>
      <description>&lt;br /&gt;
Was on vacation and couldn't get back earlier. &lt;br /&gt;
&lt;p /&gt;
Anyway, the time source for our ESX is out NTP appliance. The time source Linux VM is ESX by syncing through VMware tools.Since now the recommendation from VMware has been change to use NTP, I guess that is the route we are going to take for the VMs that are experiencing time problems.  &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
 BZ</description>
      <pubDate>Tue, 14 Apr 2009 13:25:43 GMT</pubDate>
      <author>Byron_Zhao</author>
      <guid>http://communities.vmware.com/message/1225004?tstart=0#1225004</guid>
      <dc:date>2009-04-14T13:25:43Z</dc:date>
      <clearspace:dateToText>7 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Linux VM time sync</title>
      <link>http://communities.vmware.com/message/1221117?tstart=0#1221117</link>
      <description>What is their time source?</description>
      <pubDate>Wed, 08 Apr 2009 18:46:56 GMT</pubDate>
      <author>Chamon</author>
      <guid>http://communities.vmware.com/message/1221117?tstart=0#1221117</guid>
      <dc:date>2009-04-08T18:46:56Z</dc:date>
      <clearspace:dateToText>7 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Linux VM time sync</title>
      <link>http://communities.vmware.com/message/1221085?tstart=0#1221085</link>
      <description>&lt;br /&gt;
In my previous job, we were told to sync time to ESX hosts. At that time we had about 300 VMs, and luckly we found a way to have all the Windows and Linux VM sync to the ESX hosts. It was working fine for the Windows VM and 32bit Linux VM, while some problems were still with the 64bit Linux VM. Now that this doc said I should use NTP. It is kind of frustrating. I guess I haven't followed close enough on the best practice for ESX.  &lt;br /&gt;
&lt;p /&gt;
As for ESX is the source of failure, the time in our ESX servers always have the correct time whenever I check it. &lt;br /&gt;
&lt;p /&gt;
BZ</description>
      <pubDate>Wed, 08 Apr 2009 18:42:22 GMT</pubDate>
      <author>Byron_Zhao</author>
      <guid>http://communities.vmware.com/message/1221085?tstart=0#1221085</guid>
      <dc:date>2009-04-08T18:42:22Z</dc:date>
      <clearspace:dateToText>7 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Linux VM time sync</title>
      <link>http://communities.vmware.com/message/1220777?tstart=0#1220777</link>
      <description>&lt;div class="jive-quote"&gt;page 14, it said "Whenever possible, use NTP instead of VMware Tools periodic time synchronization." &lt;/div&gt;
&lt;br /&gt;
This is the correct method.  You should ALWAYS use NTP whenever possible.  ALWAYS.  The 'synch' from the tools is a poor man's method, and it's very basic.  Plus if your server somehow get's the wrong time, ALL your VM's will now synch incorrectly, so it's best that each client get their own source.&lt;br /&gt;
&lt;br /&gt;
Even if they all point to the same NTP source, it's best to configure Linux VM's with NTP, and not use the tools.  Your ESX host woud become the source of failure if something were to happen.&lt;br /&gt;
&lt;p /&gt;
&lt;img src="http://s254920738.onlinehome.us/resources/VMW_Q109_LGO_vExpert_k.jpg" alt="http://s254920738.onlinehome.us/resources/VMW_Q109_LGO_vExpert_k.jpg" class="jive-image"  /&gt;</description>
      <pubDate>Wed, 08 Apr 2009 14:36:46 GMT</pubDate>
      <author>RParker</author>
      <guid>http://communities.vmware.com/message/1220777?tstart=0#1220777</guid>
      <dc:date>2009-04-08T14:36:46Z</dc:date>
      <clearspace:dateToText>7 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Linux VM time sync</title>
      <link>http://communities.vmware.com/message/1220646?tstart=0#1220646</link>
      <description>&lt;br /&gt;
This is an old topic, but recently a colleage draw my attention to an document at &lt;a class="jive-link-external" href="http://www.vmware.com/files/pdf/linux_install_config.pdf"&gt;Linux Install Config&lt;/a&gt;. &lt;br /&gt;
&lt;p /&gt;
I believe VMware used to recommend to use VMware tools to sync Linux VM's time clock to the ESX host. However, in this documen's page 14, it said "Whenever possible, use NTP instead of VMware Tools periodic time synchronization." &lt;br /&gt;
&lt;p /&gt;
The time issue was a real pain before. It stopped for a while. Now I see this 180 degree of change, not sure what I should follow. &lt;br /&gt;
&lt;p /&gt;
How is everyone else doing with time sync in Linux VM out there?&lt;br /&gt;
&lt;p /&gt;
BTW, my environment mainly use Red Hat.&lt;br /&gt;
&lt;p /&gt;
BZ &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Wed, 08 Apr 2009 12:53:22 GMT</pubDate>
      <author>Byron_Zhao</author>
      <guid>http://communities.vmware.com/message/1220646?tstart=0#1220646</guid>
      <dc:date>2009-04-08T12:53:22Z</dc:date>
      <clearspace:dateToText>7 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
  </channel>
</rss>

