<?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; EVC</title>
	<atom:link href="http://malaysiavm.com/blog/tag/evc/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>How to enable EVC on ESX 3.5 with No Downtime</title>
		<link>http://malaysiavm.com/blog/how-to-enable-evc-on-esx-35/</link>
		<comments>http://malaysiavm.com/blog/how-to-enable-evc-on-esx-35/#comments</comments>
		<pubDate>Mon, 08 Sep 2008 04:21:49 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[ESX 3.5]]></category>
		<category><![CDATA[EVC]]></category>
		<category><![CDATA[vmotion]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=227</guid>
		<description><![CDATA[To improve the compatibility of the Processors chipset during the VMotion for Virtualization, the recent release from VMware had the option of EVC for both INTEL and AMD which allow you to VMotion around all your VM even it is not running the same processor family. Previously you may faced compatible issues if you try [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"><!--
google_ad_client = "pub-7430566020196385";
/* MVM Index Link Code 468x15, created 1/3/10 */
google_ad_slot = "5937837755";
google_ad_width = 468;
google_ad_height = 15;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p><p>To improve the compatibility of the Processors chipset during the VMotion for Virtualization, the recent release from <a href="http://malaysiavm.com/blog/tag/vmware">VMware</a> had the option of EVC for both INTEL and AMD which allow you to <a href="http://malaysiavm.com/blog/tag/vmotion">VMotion</a> around all your VM even it is not running the same processor family. Previously you may faced compatible issues if you try to <a href="http://malaysiavm.com/blog/tag/vmotion">Vmotion</a> from INTEL 7 series to 5 series processors family. With this new option, that problem will gone. Really thanks and appreciate to the effort from VMware as well as <a href="http://malaysiavm.com/blog/tag/intel">INTEL</a> and <a href="http://malaysiavm.com/blog/tag/amd">AMD</a> to bring this success and easier our life.</p>
<p>Here I would like to share my experience on how I get this enable without interrupt my existing production environment. By default, the features will tell you to power off all your VM before you can enable this features. Here is the tweak around solution you may want to try. Most of the time, we run critical application on <a href="http://malaysiavm.com/blog/tag/vm">VM</a> which able to minimize the down time for us.</p>
<p>To have Enhanced VMotion Compatibility(<a href="http://malaysiavm.com/blog/tag/evc">EVC)</a> working, 1st you need to create a new cluster. This cluster is not necessary to have HA/DRS running itself, because is to really allow you to move the existing production VM to the temp servers. At the same time, you can setup 1 or 2 temporally ESX Server with the evaluation edition, which have similiar configuration with your production ESX. This is to allow Vmotion happen between the ESX host.</p>
<p>Once you had those ready, start to <a href="http://malaysiavm.com/blog/tag/vmotion">VMotion</a> all the VM out from the production ESX to the Newly build temporally <a href="http://malaysiavm.com/blog/tag/esx">ESX</a>, until your existing production ESX cluster is empty with any of the VM power on and running.</p>
<p><span id="more-227"></span></p>
<p>Your cluster is now ready to configure for EVC. Right click your cluster and choose Edit Setting, and click on the VMware <a href="http://malaysiavm.com/blog/tag/evc">EVC</a>. Select the option Enable EVC for Intel or AMD ( This will depend which processor you are using in your environment). Click Ok after that and the cluster will enable the EVC for you.</p>
<p><img src="http://www.malaysiavm.com/images/evc.JPG" alt="VMware EVC" /></p>
<p>Once finish, you have EVC ready for your environment and say goodbye for processor incompatible on the Vmotion. Now you can vmotion back all the VM into this HA/DRS production cluster, and decommission your temp <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> servers you just built.</p>
<p><strong>Please note that the 2 temporally ESX servers are not compatible for Vmotion before the EVC enable. </strong></p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/how-to-enable-evc-on-esx-35/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>

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

