<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Malaysia VMware Communities &#187; NTP</title>
	<atom:link href="http://malaysiavm.com/blog/tag/ntp/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2011 15:50:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Time Synchronize on VM and ESX</title>
		<link>http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/</link>
		<comments>http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/#comments</comments>
		<pubDate>Mon, 25 Aug 2008 09:56:02 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[NTP]]></category>
		<category><![CDATA[Time Synchronization]]></category>
		<category><![CDATA[VM]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=131</guid>
		<description><![CDATA[Time synchronize always important in every solution or platform. As ESX claim and advice the users to sync all the VM in ESX with the ESX host, I am here to explain why we shouldn&#8217;t do this. Recent major bugs from VMware had encountered exprie issue which disallow VM to be power on or Vmotion. [...]]]></description>
			<content:encoded><![CDATA[<p>Time synchronize always important in every solution or platform. As ESX claim and advice the users to sync all the <span id="SPELLING_ERROR_1" class="blsp-spelling-error">VM</span> in <span id="SPELLING_ERROR_2" class="blsp-spelling-error">ESX</span> with the <span id="SPELLING_ERROR_3" class="blsp-spelling-error">ESX</span> host, I am here to explain why we shouldn&#8217;t do this.</p>
<ol>
<li>Recent major bugs from <span id="SPELLING_ERROR_4" class="blsp-spelling-error">VMware</span> had encountered <span id="SPELLING_ERROR_5" class="blsp-spelling-error">exprie</span> issue which disallow <span id="SPELLING_ERROR_6" class="blsp-spelling-error">VM</span> to be power on or <span id="SPELLING_ERROR_7" class="blsp-spelling-error">Vmotion</span>. What I had done personally is &#8221; stop the <span id="SPELLING_ERROR_8" class="blsp-spelling-error">NTP</span> synchronization from <span id="SPELLING_ERROR_9" class="blsp-spelling-error">esx</span> host, and change the date back to 5 days back before the <span id="SPELLING_ERROR_10" class="blsp-spelling-error">VM</span> expire&#8221;. This easily solve my issue and allow me to <span id="SPELLING_ERROR_11" class="blsp-spelling-error">Vmotion</span> all the <span id="SPELLING_ERROR_12" class="blsp-spelling-error">VM</span> machine to another destination host without any <span id="SPELLING_ERROR_13" class="blsp-spelling-corrected">interruption</span>. Can you imagine if you sync all the <span id="SPELLING_ERROR_14" class="blsp-spelling-error">VM</span> with <a href="http://malaysiavm.com/blog/tag/vmware/" target="_self"><span id="SPELLING_ERROR_15" class="blsp-spelling-error">ESX</span></a> host, you will lose this flexibility and in the big pain to figure out, how would you able to simplify the patch process to fix the bugs even <a href="http://malaysiavm.com/blog/tag/vmware/" target="_self"><span id="SPELLING_ERROR_16" class="blsp-spelling-error">VMware</span></a> had released the bug fix</li>
<li>I still do not see any potential issues with the current configuration that we sync all the <a href="http://malaysiavm.com/blog/tag/vmware/" target="_self"><span id="SPELLING_ERROR_17" class="blsp-spelling-error">VM</span></a> and physical servers to multiple <span id="SPELLING_ERROR_18" class="blsp-spelling-error">NTP</span> servers we do have in our environment. Standardization always important as if we can minimize the different method of support and <span id="SPELLING_ERROR_19" class="blsp-spelling-corrected">maintenance</span>, it will help to reduce complexity.<span id="more-131"></span></li>
<li>If you <a href="http://malaysiavm.com/blog/tag/vmware/" target="_self"><span id="SPELLING_ERROR_20" class="blsp-spelling-error">VM</span></a> is running on windows, the <span id="SPELLING_ERROR_21" class="blsp-spelling-error">VM</span> will direct synchronize with the time servers in AD by default, and I don&#8217;t really see the potential need to create another specify way to synchronize the time on the <a href="http://malaysiavm.com/blog/tag/vmware/" target="_self"><span id="SPELLING_ERROR_22" class="blsp-spelling-error">VM</span></a>.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/time-synchronize-on-vm-and-esx/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.325 seconds -->

