<?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: VMotion stops working in vSphere</title>
	<atom:link href="http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/</link>
	<description>Surplus Verbiage from a VMware Employee</description>
	<lastBuildDate>Fri, 12 Mar 2010 16:19:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard Jones</title>
		<link>http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/comment-page-1/#comment-664</link>
		<dc:creator>Richard Jones</dc:creator>
		<pubDate>Tue, 29 Sep 2009 09:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/#comment-664</guid>
		<description>I joust found a similar article here. This guy manually edited the .vmx file to resolve the issue:

http://www.jjclements.co.uk/index.php/2009/09/15/vmware-vmotion-cpu-problem-after-vsphere-upgrade</description>
		<content:encoded><![CDATA[<p>I joust found a similar article here. This guy manually edited the .vmx file to resolve the issue:</p>
<p><a href="http://www.jjclements.co.uk/index.php/2009/09/15/vmware-vmotion-cpu-problem-after-vsphere-upgrade" rel="nofollow">http://www.jjclements.co.uk/index.php/2009/09/15/vmware-vmotion-cpu-problem-after-vsphere-upgrade</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/comment-page-1/#comment-660</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 25 Sep 2009 13:36:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/#comment-660</guid>
		<description>So - I have verified all these things and STILL vMotion isn&#039;t working for me.  These are fresh installs - not upgrades.  The flag is always there - machine has to be powered off to perform this function....

Dell poweredge 2950&#039;s that had 3.5 update 2 on them.  vMotion worked before installing 4.0 on the servers....any ideas?</description>
		<content:encoded><![CDATA[<p>So &#8211; I have verified all these things and STILL vMotion isn&#8217;t working for me.  These are fresh installs &#8211; not upgrades.  The flag is always there &#8211; machine has to be powered off to perform this function&#8230;.</p>
<p>Dell poweredge 2950&#8217;s that had 3.5 update 2 on them.  vMotion worked before installing 4.0 on the servers&#8230;.any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Return of Virtualization Short Takes - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</title>
		<link>http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/comment-page-1/#comment-530</link>
		<dc:creator>The Return of Virtualization Short Takes - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</dc:creator>
		<pubDate>Fri, 05 Jun 2009 17:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/#comment-530</guid>
		<description>[...] to VMware vSphere, and now having issues with VMotion? Thanks to VMwarewolf, this pair of VMware KB articles (here and here) might help resolve the [...]</description>
		<content:encoded><![CDATA[<p>[...] to VMware vSphere, and now having issues with VMotion? Thanks to VMwarewolf, this pair of VMware KB articles (here and here) might help resolve the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi</title>
		<link>http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/comment-page-1/#comment-521</link>
		<dc:creator>Tomi</dc:creator>
		<pubDate>Wed, 27 May 2009 12:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/#comment-521</guid>
		<description>Even though I am &quot;pro VMware&quot; admin I&#039;d say that KB1011294 issue is not minor hiccup. Requirement to power off an VM after migration from ESX 3 to ESX 4 to get VMotion working is quite big problem for me and my clients.</description>
		<content:encoded><![CDATA[<p>Even though I am &#8220;pro VMware&#8221; admin I&#8217;d say that KB1011294 issue is not minor hiccup. Requirement to power off an VM after migration from ESX 3 to ESX 4 to get VMotion working is quite big problem for me and my clients.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A C</title>
		<link>http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/comment-page-1/#comment-520</link>
		<dc:creator>A C</dc:creator>
		<pubDate>Tue, 26 May 2009 17:02:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-stops-working-in-vsphere/#comment-520</guid>
		<description>Now that is a brilliant piece of Quality Assurance. vSphere 4 wasn&#039;t rushed. Seriously. Trust me.</description>
		<content:encoded><![CDATA[<p>Now that is a brilliant piece of Quality Assurance. vSphere 4 wasn&#8217;t rushed. Seriously. Trust me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
