<?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"
	>
<channel>
	<title>Comments on: VMotion Arrogance &#038; Humility at VMworld Cannes</title>
	<atom:link href="http://www.thevirtualblackhole.com/virtual-marketing/vmotion-arrogance-humility-at-vmworld-cannes/feed" rel="self" type="application/rss+xml" />
	<link>http://www.thevirtualblackhole.com/virtual-marketing/vmotion-arrogance-humility-at-vmworld-cannes</link>
	<description>The Virtual Black Hole</description>
	<pubDate>Thu, 29 Jul 2010 23:56:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Jason Boche</title>
		<link>http://www.thevirtualblackhole.com/virtual-marketing/vmotion-arrogance-humility-at-vmworld-cannes#comment-248</link>
		<dc:creator>Jason Boche</dc:creator>
		<pubDate>Mon, 02 Mar 2009 23:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thevirtualblackhole.com/?p=619#comment-248</guid>
		<description>Believe it or not, I ran into a situation over the weekend in production where VMotion was working, however, it was taking an EXTREMELY long time (20+ minutes for a VM with 4GB vRAM).  After some quick digging, I found out the pNIC on the source ESX host had reverted from its orginally negotiated speed of 1000Mbps (1Gbps) to 100Mbps.  The problem lies somewhere between the pNIC and the switch port.  The network guys assure me the switch port is configured for 1Gbps.  Bad cable is a long shot but I won't rule that out either.

The point of my story is that I could have used a product like OpsCheck to let me know I had a poorly configured pNIC attached to the VMKernel switch that handles VMotion.  I don't want to wait until a maintenance window where time is short to find this out.  I would have liked to have been notified the moment that pNIC changed speeds from 1000Mbps to 100Mbps.  Who knows when it happened - a day ago.  A week ago.  A month ago.

Jas</description>
		<content:encoded><![CDATA[<p>Believe it or not, I ran into a situation over the weekend in production where VMotion was working, however, it was taking an EXTREMELY long time (20+ minutes for a VM with 4GB vRAM).  After some quick digging, I found out the pNIC on the source ESX host had reverted from its orginally negotiated speed of 1000Mbps (1Gbps) to 100Mbps.  The problem lies somewhere between the pNIC and the switch port.  The network guys assure me the switch port is configured for 1Gbps.  Bad cable is a long shot but I won&#8217;t rule that out either.</p>
<p>The point of my story is that I could have used a product like OpsCheck to let me know I had a poorly configured pNIC attached to the VMKernel switch that handles VMotion.  I don&#8217;t want to wait until a maintenance window where time is short to find this out.  I would have liked to have been notified the moment that pNIC changed speeds from 1000Mbps to 100Mbps.  Who knows when it happened - a day ago.  A week ago.  A month ago.</p>
<p>Jas</p>
]]></content:encoded>
	</item>
</channel>
</rss>
