<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Matrix to Determine VMotion Compatibility by Processor</title>
	<atom:link href="http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Wed, 25 Jan 2012 13:41:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: What is Enhanced vMotion compatibility &#124; ESX Virtualization</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-2676</link>
		<dc:creator>What is Enhanced vMotion compatibility &#124; ESX Virtualization</dc:creator>
		<pubDate>Mon, 22 Jun 2009 16:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-2676</guid>
		<description>[...] So with this in my mind I went to Rich Bramley&#8217;s blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] So with this in my mind I went to Rich Bramley&#8217;s blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Best Registry Cleaner</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-2246</link>
		<dc:creator>Best Registry Cleaner</dc:creator>
		<pubDate>Tue, 24 Mar 2009 01:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-2246</guid>
		<description>i&#039;ve got the same problem, and i found the solution here on &lt;a href=&quot;http://windowsfix.info/fix-blue-screen/&quot; rel=&quot;nofollow&quot;&gt;&lt;b&gt;Fix Blue Screen Error&lt;/b&gt;&lt;/a&gt;, just for reference.</description>
		<content:encoded><![CDATA[<p>i&#39;ve got the same problem, and i found the solution here on <a href="http://windowsfix.info/fix-blue-screen/" rel="nofollow"><b>Fix Blue Screen Error</b></a>, just for reference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enhanced Vmotion Compatibility (EVC) – Intel Example - Gestalt IT - Gestalt IT</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-2043</link>
		<dc:creator>Enhanced Vmotion Compatibility (EVC) – Intel Example - Gestalt IT - Gestalt IT</dc:creator>
		<pubDate>Fri, 13 Feb 2009 02:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-2043</guid>
		<description>[...] Example  Nov 16th, 2008 &#124; Category: Server Virtualization   A reader named Tom commented on my Matrix to Determine VMotion Compatibility by Processor post today [...]</description>
		<content:encoded><![CDATA[<p>[...] Example  Nov 16th, 2008 | Category: Server Virtualization   A reader named Tom commented on my Matrix to Determine VMotion Compatibility by Processor post today [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bethany K Ford</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-2002</link>
		<dc:creator>Bethany K Ford</dc:creator>
		<pubDate>Tue, 03 Feb 2009 23:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-2002</guid>
		<description>nice article! nice site. you&#039;re in my rss feed now ;-)&lt;br&gt;keep it up</description>
		<content:encoded><![CDATA[<p>nice article! nice site. you&#39;re in my rss feed now <img src='http://vmetc.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> <br />keep it up</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enhanced Vmotion Compatibility (EVC) – Intel Example &#124; VM /ETC</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-1500</link>
		<dc:creator>Enhanced Vmotion Compatibility (EVC) – Intel Example &#124; VM /ETC</dc:creator>
		<pubDate>Mon, 17 Nov 2008 04:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-1500</guid>
		<description>[...] reader named Tom commented on my Matrix to Determine VMotion Compatibility by Processor post today [...]</description>
		<content:encoded><![CDATA[<p>[...] reader named Tom commented on my Matrix to Determine VMotion Compatibility by Processor post today [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-1499</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Mon, 17 Nov 2008 02:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-1499</guid>
		<description>Tom,

Actually, vmotion boundaries between cpu chips may seem to have evolved some with the announcement of VMware&#039;s Enhanced Vmotion feature, and the ability to migrate between Amd and Intel has certainly been in the spotlight recently, but the issue is still the same. That is, all vendor&#039;s virtualization hosts check for like cpu families before live migration. If you decide to mask this safety check then any live migration is possible (all of hypervisors can do this). But this is just an ability and not a technical certainty. It may work 4 out of 5 times, but that 5th time when the application needs the instruction set that does not exist on the migration target the VM will blue screen.

Mike D explains it best http://mikedatl.typepad.com/mikedvirtualization/2008/02/migrating-from.html</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>Actually, vmotion boundaries between cpu chips may seem to have evolved some with the announcement of VMware&#8217;s Enhanced Vmotion feature, and the ability to migrate between Amd and Intel has certainly been in the spotlight recently, but the issue is still the same. That is, all vendor&#8217;s virtualization hosts check for like cpu families before live migration. If you decide to mask this safety check then any live migration is possible (all of hypervisors can do this). But this is just an ability and not a technical certainty. It may work 4 out of 5 times, but that 5th time when the application needs the instruction set that does not exist on the migration target the VM will blue screen.</p>
<p>Mike D explains it best <a href="http://mikedatl.typepad.com/mikedvirtualization/2008/02/migrating-from.html" rel="nofollow">http://mikedatl.typepad.com/mikedvirtualization/2008/02/migrating-from.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-5232</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Mon, 17 Nov 2008 02:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-5232</guid>
		<description>Tom,

Actually, vmotion boundaries between cpu chips may seem to have evolved some with the announcement of VMware&#039;s Enhanced Vmotion feature, and the ability to migrate between Amd and Intel has certainly been in the spotlight recently, but the issue is still the same. That is, all vendor&#039;s virtualization hosts check for like cpu families before live migration. If you decide to mask this safety check then any live migration is possible (all of hypervisors can do this). But this is just an ability and not a technical certainty. It may work 4 out of 5 times, but that 5th time when the application needs the instruction set that does not exist on the migration target the VM will blue screen.

Mike D explains it best http://mikedatl.typepad.com/mikedvirtualization/2008/02/migrating-from.html</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>Actually, vmotion boundaries between cpu chips may seem to have evolved some with the announcement of VMware&#8217;s Enhanced Vmotion feature, and the ability to migrate between Amd and Intel has certainly been in the spotlight recently, but the issue is still the same. That is, all vendor&#8217;s virtualization hosts check for like cpu families before live migration. If you decide to mask this safety check then any live migration is possible (all of hypervisors can do this). But this is just an ability and not a technical certainty. It may work 4 out of 5 times, but that 5th time when the application needs the instruction set that does not exist on the migration target the VM will blue screen.</p>
<p>Mike D explains it best <a href="http://mikedatl.typepad.com/mikedvirtualization/2008/02/migrating-from.html" rel="nofollow">http://mikedatl.typepad.com/mikedvirtualization/2008/02/migrating-from.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://vmetc.com/2008/06/19/matrix-to-determine-vmotion-compatibility-by-processor/comment-page-1/#comment-1497</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 16 Nov 2008 23:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=430#comment-1497</guid>
		<description>If it has been shown possible to do VMotion between Intel and AMD processors, which are even more different than many Intel chips are different from each other, has VMotion evolved at all to the point where differences between Intel chips are less of an issue than they were in June when you blogged this??

Thank you, Tom</description>
		<content:encoded><![CDATA[<p>If it has been shown possible to do VMotion between Intel and AMD processors, which are even more different than many Intel chips are different from each other, has VMotion evolved at all to the point where differences between Intel chips are less of an issue than they were in June when you blogged this??</p>
<p>Thank you, Tom</p>
]]></content:encoded>
	</item>
</channel>
</rss>

