<?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 fails at 10 percent</title>
	<atom:link href="http://www.vmwarewolf.com/vmotion-fails-at-10-percent/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/</link>
	<description>Surplus Verbiage from a VMware Employee</description>
	<lastBuildDate>Tue, 27 Apr 2010 19:20:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: SunilN</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-1091</link>
		<dc:creator>SunilN</dc:creator>
		<pubDate>Fri, 26 Feb 2010 16:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-1091</guid>
		<description>vmotion worked..I had the third esx vmotion switch on wrong IP segment..Thank you for all your inputs.</description>
		<content:encoded><![CDATA[<p>vmotion worked..I had the third esx vmotion switch on wrong IP segment..Thank you for all your inputs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SteveP</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-737</link>
		<dc:creator>SteveP</dc:creator>
		<pubDate>Tue, 13 Oct 2009 21:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-737</guid>
		<description>Awesome!  I am having storage vMotion fail at 10% with a timeout.  I have suspected some of these as the cause, it is very nice to have this list as a checklist.  This should keep me busy for a day or two.</description>
		<content:encoded><![CDATA[<p>Awesome!  I am having storage vMotion fail at 10% with a timeout.  I have suspected some of these as the cause, it is very nice to have this list as a checklist.  This should keep me busy for a day or two.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: l.veirman</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-668</link>
		<dc:creator>l.veirman</dc:creator>
		<pubDate>Wed, 30 Sep 2009 23:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-668</guid>
		<description>Hi,

Just in case it could be helpful to anyone else : the VMotion will time out when you modify the datastorage of your cluster (meaning, for exemple, removing one VMFS and replace it with three new one).

You&#039;ll need then to stop the VM and do the &quot;migrate&quot; action. you&#039;ll then be prompt to let ESX knows where to store the disk (option &quot;keep in the same location is then greyed out but with the advanced settings you&#039;ll fond back the same action).

Cheers.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Just in case it could be helpful to anyone else : the VMotion will time out when you modify the datastorage of your cluster (meaning, for exemple, removing one VMFS and replace it with three new one).</p>
<p>You&#8217;ll need then to stop the VM and do the &#8220;migrate&#8221; action. you&#8217;ll then be prompt to let ESX knows where to store the disk (option &#8220;keep in the same location is then greyed out but with the advanced settings you&#8217;ll fond back the same action).</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter G.</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-499</link>
		<dc:creator>Peter G.</dc:creator>
		<pubDate>Wed, 06 May 2009 16:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-499</guid>
		<description>One more possibility that we recently ran into.  All the guests on a host would vmotion except one.  It would get to 10% and then fail.  Tried all the suggestions above but it still wouldn&#039;t budge.  Finally found the issue - for some reason HA had gone beserk a few weeks earlier and caused the host to create nearly 5000 log files in the VM&#039;s folder on the SAN.  After deleting all but the current log file the guest vmotioned without any issues.</description>
		<content:encoded><![CDATA[<p>One more possibility that we recently ran into.  All the guests on a host would vmotion except one.  It would get to 10% and then fail.  Tried all the suggestions above but it still wouldn&#8217;t budge.  Finally found the issue &#8211; for some reason HA had gone beserk a few weeks earlier and caused the host to create nearly 5000 log files in the VM&#8217;s folder on the SAN.  After deleting all but the current log file the guest vmotioned without any issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas H.</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-488</link>
		<dc:creator>Thomas H.</dc:creator>
		<pubDate>Wed, 01 Apr 2009 12:42:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-488</guid>
		<description>We hat the 10% issue on a customers cluster, too. Problem: another network device (HP ILO) had the same IP as the kernel interface of one of the cluster nodes. The VMs did not report that in any log. After changing the kernel IP to an unused address the 10% issue was resolved immediately.</description>
		<content:encoded><![CDATA[<p>We hat the 10% issue on a customers cluster, too. Problem: another network device (HP ILO) had the same IP as the kernel interface of one of the cluster nodes. The VMs did not report that in any log. After changing the kernel IP to an unused address the 10% issue was resolved immediately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Mellor</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-401</link>
		<dc:creator>Gary Mellor</dc:creator>
		<pubDate>Thu, 08 Jan 2009 08:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-401</guid>
		<description>I&#039;ve just resolved an issue which was causing one of my VMs to fail a VMotion at 10% too. Other VMs were fine, it was just this one. Suggested additional entry :

11) Check VMs vmware.log for error messages. 

Somehow the .vmx file workingDir= entry had managed to drop the last character, the log file reported &quot;This virtual machine cannot be powered on because its working directory is not valid&quot;. VC only reported a Timeout error, so it was only the vmware.log file which showed the actual error.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just resolved an issue which was causing one of my VMs to fail a VMotion at 10% too. Other VMs were fine, it was just this one. Suggested additional entry :</p>
<p>11) Check VMs vmware.log for error messages. </p>
<p>Somehow the .vmx file workingDir= entry had managed to drop the last character, the log file reported &#8220;This virtual machine cannot be powered on because its working directory is not valid&#8221;. VC only reported a Timeout error, so it was only the vmware.log file which showed the actual error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan D.</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-386</link>
		<dc:creator>Bryan D.</dc:creator>
		<pubDate>Tue, 16 Dec 2008 18:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-386</guid>
		<description>Another thing to try would be reconfiguring (flipping) your Vmotion NIC settings between 1000/Full and Auto-Negotiate (or whatever fits your network&#039;s speed).  This resolved our &#039;VMotion failing at 10%&#039; issue.  I believe we have a port auto-sensing problem with our switches.</description>
		<content:encoded><![CDATA[<p>Another thing to try would be reconfiguring (flipping) your Vmotion NIC settings between 1000/Full and Auto-Negotiate (or whatever fits your network&#8217;s speed).  This resolved our &#8216;VMotion failing at 10%&#8217; issue.  I believe we have a port auto-sensing problem with our switches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart V</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-375</link>
		<dc:creator>Bart V</dc:creator>
		<pubDate>Fri, 05 Dec 2008 10:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-375</guid>
		<description>Hi,

this can occur also when the &quot;receiving&quot; ESX server has I/O errors.
A rescan of the storage can help in this case.

Regards,

Bart</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>this can occur also when the &#8220;receiving&#8221; ESX server has I/O errors.<br />
A rescan of the storage can help in this case.</p>
<p>Regards,</p>
<p>Bart</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-350</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 17 Jul 2008 16:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-350</guid>
		<description>Links have been fixed!
Sorry for the inconvenience!</description>
		<content:encoded><![CDATA[<p>Links have been fixed!<br />
Sorry for the inconvenience!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Irene</title>
		<link>http://www.vmwarewolf.com/vmotion-fails-at-10-percent/comment-page-1/#comment-349</link>
		<dc:creator>Irene</dc:creator>
		<pubDate>Wed, 16 Jul 2008 14:26:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmwarewolf.com/vmotion-fails-at-10-percent/#comment-349</guid>
		<description>Hi,

Our ESX Servers (3.5U1) do have some major vmotion issues. can you send me valid links to the documents, the published links are broken.

thanks,
Irene</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Our ESX Servers (3.5U1) do have some major vmotion issues. can you send me valid links to the documents, the published links are broken.</p>
<p>thanks,<br />
Irene</p>
]]></content:encoded>
	</item>
</channel>
</rss>
