<?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: Upgrade your Virtual Hardware in a few minutes, with a twist.</title>
	<atom:link href="http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/</link>
	<description>a technology blog with a focus on virtualization and cloud computing</description>
	<lastBuildDate>Tue, 07 Sep 2010 16:40:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ajay</title>
		<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/comment-page-1/#comment-2280</link>
		<dc:creator>Ajay</dc:creator>
		<pubDate>Sat, 28 Aug 2010 11:20:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualinsanity.com/?p=741#comment-2280</guid>
		<description>These requirements are not so bad. It&#039;s something that I&#039;ve expected, and I&#039;ve already got my eyes on a used computer hardware place so I start renewing everything. Thank you for the info.</description>
		<content:encoded><![CDATA[<p>These requirements are not so bad. It&#39;s something that I&#39;ve expected, and I&#39;ve already got my eyes on a used computer hardware place so I start renewing everything. Thank you for the info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MrLoftcraft</title>
		<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/comment-page-1/#comment-2246</link>
		<dc:creator>MrLoftcraft</dc:creator>
		<pubDate>Mon, 02 Aug 2010 10:42:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualinsanity.com/?p=741#comment-2246</guid>
		<description>I guess we have to wait a little bit for some feedback from people that actually upgraded to version 7.0 and see how they manage with it. We could debate for hours here, but the real thing is always what counts.</description>
		<content:encoded><![CDATA[<p>I guess we have to wait a little bit for some feedback from people that actually upgraded to version 7.0 and see how they manage with it. We could debate for hours here, but the real thing is always what counts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VM Dude</title>
		<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/comment-page-1/#comment-2126</link>
		<dc:creator>VM Dude</dc:creator>
		<pubDate>Thu, 20 May 2010 10:25:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualinsanity.com/?p=741#comment-2126</guid>
		<description>Makes it look simple, sure but what is done above is trivial to the process as far as the big picture goes for an Enterprise. The amount of paperwork/red tape work that this type of thing done against a massive number of VMs is the real issue. Getting an outage for so many VMs, coordinating outages for VMs with dependencies, Change Management will require backups and rollback options (rollback for hw upgrade can be a copy of the .vmx file before) etc... This is where the real time is consumed in such an upgrade</description>
		<content:encoded><![CDATA[<p>Makes it look simple, sure but what is done above is trivial to the process as far as the big picture goes for an Enterprise. The amount of paperwork/red tape work that this type of thing done against a massive number of VMs is the real issue. Getting an outage for so many VMs, coordinating outages for VMs with dependencies, Change Management will require backups and rollback options (rollback for hw upgrade can be a copy of the .vmx file before) etc&#8230; This is where the real time is consumed in such an upgrade</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sketchy00</title>
		<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/comment-page-1/#comment-2081</link>
		<dc:creator>sketchy00</dc:creator>
		<pubDate>Fri, 05 Mar 2010 20:00:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualinsanity.com/?p=741#comment-2081</guid>
		<description>Ah... yeah, I suppose when you are putting it in the context of 1,000 vms, I can now understand what you were attempting to demonstrate.  I was kicking myself a bit for what was an otherwise great upgrade process to vsphere, and I simply didn&#039;t pay enough attention to the virtual hardware upgrade.  The ease of upgrading from virtual hardware 4 to 7 made me trivialize the matter.  ...my bad.&lt;br&gt;&lt;br&gt;Keep up the great posts.</description>
		<content:encoded><![CDATA[<p>Ah&#8230; yeah, I suppose when you are putting it in the context of 1,000 vms, I can now understand what you were attempting to demonstrate.  I was kicking myself a bit for what was an otherwise great upgrade process to vsphere, and I simply didn&#39;t pay enough attention to the virtual hardware upgrade.  The ease of upgrading from virtual hardware 4 to 7 made me trivialize the matter.  &#8230;my bad.</p>
<p>Keep up the great posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scottsauer</title>
		<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/comment-page-1/#comment-2080</link>
		<dc:creator>scottsauer</dc:creator>
		<pubDate>Fri, 05 Mar 2010 18:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualinsanity.com/?p=741#comment-2080</guid>
		<description>Sketchy00,&lt;br&gt;Thanks for the comments.  What I was trying to suggest is that there is a lot of work involved in upgrading to vSphere, and this is only one of the steps that needs to be performed as part of the upgrade process.  We have an environment that consists of ~1000 virtual machines so my attempt was to try to demonstrate how quickly you can knock this out.  &lt;br&gt;&lt;br&gt;Introducing a change in your environment is always going to open you up to some risk.  I suggest creating snapshots and testing this process out before you upgrade your production virtual machine environment.  Snapshots will in fact capture changes that take place when going from version 4 to version 7.&lt;br&gt;&lt;br&gt;I read your article and that is great technical feedback for users to be aware of as they are going through this process.</description>
		<content:encoded><![CDATA[<p>Sketchy00,<br />Thanks for the comments.  What I was trying to suggest is that there is a lot of work involved in upgrading to vSphere, and this is only one of the steps that needs to be performed as part of the upgrade process.  We have an environment that consists of ~1000 virtual machines so my attempt was to try to demonstrate how quickly you can knock this out.  </p>
<p>Introducing a change in your environment is always going to open you up to some risk.  I suggest creating snapshots and testing this process out before you upgrade your production virtual machine environment.  Snapshots will in fact capture changes that take place when going from version 4 to version 7.</p>
<p>I read your article and that is great technical feedback for users to be aware of as they are going through this process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sketchy00</title>
		<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/comment-page-1/#comment-2066</link>
		<dc:creator>sketchy00</dc:creator>
		<pubDate>Thu, 04 Mar 2010 20:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualinsanity.com/?p=741#comment-2066</guid>
		<description>Screwing up machines is always faster than fixing them.  It sounds like you are suggesting that the speed and hasle of touching VM&#039;s when changing them over to Virtual Hardware level 7 is the reason behind the population not doing so.  I think there is more to it.  I wrote about my experiences to upgrading VMs to level 7 here:  &lt;a href=&quot;http://itforme.wordpress.com/2010/01/17/side-effects-of-upgrading-vms-to-virtual-hardware-7-in-vsphere/&quot; rel=&quot;nofollow&quot;&gt;http://itforme.wordpress.com/2010/01/17/side-ef...&lt;/a&gt;  &lt;br&gt;&lt;br&gt;Hope this saves someone&#039;s tail.</description>
		<content:encoded><![CDATA[<p>Screwing up machines is always faster than fixing them.  It sounds like you are suggesting that the speed and hasle of touching VM&#39;s when changing them over to Virtual Hardware level 7 is the reason behind the population not doing so.  I think there is more to it.  I wrote about my experiences to upgrading VMs to level 7 here:  <a href="http://itforme.wordpress.com/2010/01/17/side-effects-of-upgrading-vms-to-virtual-hardware-7-in-vsphere/" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/itforme.wordpress.com/2010/01/17/side-effects-of-upgrading-vms-to-virtual-hardware-7-in-vsphere/?referer=');"></a><a href="http://itforme.wordpress.com/2010/01/17/side-ef.." rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/itforme.wordpress.com/2010/01/17/side-ef..?referer=');">http://itforme.wordpress.com/2010/01/17/side-ef..</a>.  </p>
<p>Hope this saves someone&#39;s tail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jasonspruance</title>
		<link>http://www.virtualinsanity.com/index.php/2010/03/03/upgrade-your-virtual-hardware-in-a-few-minutes-with-a-twist/comment-page-1/#comment-2064</link>
		<dc:creator>jasonspruance</dc:creator>
		<pubDate>Thu, 04 Mar 2010 01:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.virtualinsanity.com/?p=741#comment-2064</guid>
		<description>Nice post.  You are right, it only takes a few minutes.</description>
		<content:encoded><![CDATA[<p>Nice post.  You are right, it only takes a few minutes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
