 




<?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>Irregular Expressions &#187; vmware-cmd</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/Irregular-Expressions/tag/vmware-cmd/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions</link>
	<description>Insight into current security related events and exploits, including virtualization security and tips.</description>
	<lastBuildDate>Sun, 28 Apr 2013 08:00:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Recovering from a failed DMotion</title>
		<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/recovering-from-a-failed-dmotion/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/recovering-from-a-failed-dmotion/#comments</comments>
		<pubDate>Sat, 20 Feb 2010 04:37:55 +0000</pubDate>
		<dc:creator>Dan O'Connor</dc:creator>
				<category><![CDATA[dmotion]]></category>
		<category><![CDATA[failed dmotion]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[vmware-cmd]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Irregular-Expressions/?p=69</guid>
		<description><![CDATA[A few weeks back I was asked to recover a ESX 3.5 host that had VM that was in a strange state.  The VM was supposed to have been DMotion over to another datastore but it had failed.  The VM was still running but no operations were possible on it, I could not edit it [...]]]></description>
				<content:encoded><![CDATA[<p>A few weeks back I was asked to recover a ESX 3.5 host that had VM that was in a strange state.  The VM was supposed to have been DMotion over to another datastore but it had failed.  The VM was still running but no operations were possible on it, I could not edit it or control the power state.</p>
<p>When I checked the datastore with the VM it had it&#8217;s disks in the original datastore but the rest of the vm had been moved to the new location.</p>
<p>The datastore with the disks had several files inside that looked like snapshot files but named differently.  In the virtual center console I tried to take / commit a snap shot thinking it might commit the disks and the DMotion files but it was the same as the rest of the options.</p>
<p>I was how ever able to commit the disks using the command line utilities on the console.  By first creating a snapshot, them committing them. ( vmware-cmd ) is used for that.  DMotion is something that I had never used before so after a quick bit of research I found the rest of the steps to recovery the VM back to a stable state.</p>
<p>The VM still thought it was being moved so you have to manually edit the vmx file.</p>
<p>The full instructions are here, http://www.van-lieshout.com/2009/03/how-to-recover-from-failed-svmotion/</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/recovering-from-a-failed-dmotion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
