<?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>thinking sysadmin &#187; vmotion</title>
	<atom:link href="http://andyleonard.com/tag/vmotion/feed/" rel="self" type="application/rss+xml" />
	<link>http://andyleonard.com</link>
	<description>qstat -u aleonard -s z</description>
	<lastBuildDate>Tue, 28 Feb 2012 04:47:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>VMware: Not kidding about VMotion GigE Requirement</title>
		<link>http://andyleonard.com/2009/02/03/vmware-not-kidding-about-vmotion-gige-requirement/</link>
		<comments>http://andyleonard.com/2009/02/03/vmware-not-kidding-about-vmotion-gige-requirement/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 00:42:06 +0000</pubDate>
		<dc:creator>Andy</dc:creator>
				<category><![CDATA[virtualization]]></category>
		<category><![CDATA[ethernet]]></category>
		<category><![CDATA[vmotion]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://andyleonard.com/?p=206</guid>
		<description><![CDATA[In case you&#8217;re curious/adventurous/broke enough to try configuring your VMotion network on Fast Ethernet instead of Gigabit Ethernet, here&#8217;s what you can expect. First, a warning from your VI client that you&#8217;re venturing into unsupported territory: And then, if you go ahead with the VMotion, a slight pause on the VM in question.  The following [...]]]></description>
			<content:encoded><![CDATA[<p>In case you&#8217;re curious/adventurous/broke enough to try configuring your VMotion network on Fast Ethernet instead of Gigabit Ethernet, here&#8217;s what you can expect.</p>
<p>First, a warning from your VI client that you&#8217;re venturing into unsupported territory:</p>
<div id="attachment_208" class="wp-caption aligncenter" style="width: 310px"><a href="http://andyleonard.com/wp-content/uploads/2009/02/vmotion.png"><img class="size-medium wp-image-208" title="vmotion" src="http://andyleonard.com/wp-content/uploads/2009/02/vmotion-300x182.png" alt="A friendly warning" width="300" height="182" /></a><p class="wp-caption-text">A friendly warning</p></div>
<p>And then, if you go ahead with the VMotion, a slight pause on the VM in question.  The following is output from running <code>while true; do date; sleep 1; done</code> on a Linux guest during the VMotion:</p>
<pre>Tue Feb  3 13:23:17 PST 2009
Tue Feb  3 13:23:18 PST 2009
Tue Feb  3 13:23:19 PST 2009
Tue Feb  3 13:23:20 PST 2009
Tue Feb  3 13:23:21 PST 2009
Tue Feb  3 13:23:22 PST 2009
Tue Feb  3 13:24:12 PST 2009
Tue Feb  3 13:24:13 PST 2009
Tue Feb  3 13:24:14 PST 2009
Tue Feb  3 13:24:15 PST 2009
Tue Feb  3 13:24:16 PST 2009</pre>
<p>Note the fifty second pause between 13:23:22 and 13:24:12?  Ouch&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://andyleonard.com/2009/02/03/vmware-not-kidding-about-vmotion-gige-requirement/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

