<?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: Deploying VMware in a Linux Shop #PO2575</title>
	<atom:link href="http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Tue, 17 Apr 2012 03:50:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Mike DiPetrillo</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-1400</link>
		<dc:creator>Mike DiPetrillo</dc:creator>
		<pubDate>Sat, 18 Oct 2008 12:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-1400</guid>
		<description>J, if you want you can email me off-line to figure out what&#039;s going on: http://www.mikedipetrillo.com/about.html. Where are you getting the values from? Virtual Center? esxtop?</description>
		<content:encoded><![CDATA[<p>J, if you want you can email me off-line to figure out what&#8217;s going on: <a href="http://www.mikedipetrillo.com/about.html" rel="nofollow">http://www.mikedipetrillo.com/about.html</a>. Where are you getting the values from? Virtual Center? esxtop?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike DiPetrillo</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-5438</link>
		<dc:creator>Mike DiPetrillo</dc:creator>
		<pubDate>Sat, 18 Oct 2008 12:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-5438</guid>
		<description>J, if you want you can email me off-line to figure out what&#039;s going on: http://www.mikedipetrillo.com/about.html. Where are you getting the values from? Virtual Center? esxtop?</description>
		<content:encoded><![CDATA[<p>J, if you want you can email me off-line to figure out what&#8217;s going on: <a href="http://www.mikedipetrillo.com/about.html" rel="nofollow">http://www.mikedipetrillo.com/about.html</a>. Where are you getting the values from? Virtual Center? esxtop?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-1396</link>
		<dc:creator>J</dc:creator>
		<pubDate>Fri, 17 Oct 2008 15:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-1396</guid>
		<description>Thanks Mike and Rich,vary very interesting. 
It was exactly what I was supposing. I&#039;m seeing 20% RDY (average) in my hosts (sometimes 45%...). Most of the VMs are configured with 2vCPU and are VMs with little load.
The extrange thing is that I&#039;m seeing 400 or 500 or 600 as values for the %WAIT parameter!!
Is it a bug? I&#039;ve to read this like 40 or 50 or 60% values? May be I &#039;ve to read the %TWAIT or %BWAIT calues insted the %WAIT value?
Or may be it&#039;s correct.
This seems to happen both in ESX 3.0.2 and ESX 3.5.

TIA,
J</description>
		<content:encoded><![CDATA[<p>Thanks Mike and Rich,vary very interesting.<br />
It was exactly what I was supposing. I&#8217;m seeing 20% RDY (average) in my hosts (sometimes 45%&#8230;). Most of the VMs are configured with 2vCPU and are VMs with little load.<br />
The extrange thing is that I&#8217;m seeing 400 or 500 or 600 as values for the %WAIT parameter!!<br />
Is it a bug? I&#8217;ve to read this like 40 or 50 or 60% values? May be I &#8216;ve to read the %TWAIT or %BWAIT calues insted the %WAIT value?<br />
Or may be it&#8217;s correct.<br />
This seems to happen both in ESX 3.0.2 and ESX 3.5.</p>
<p>TIA,<br />
J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-5444</link>
		<dc:creator>J</dc:creator>
		<pubDate>Fri, 17 Oct 2008 15:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-5444</guid>
		<description>Thanks Mike and Rich,vary very interesting. 
It was exactly what I was supposing. I&#039;m seeing 20% RDY (average) in my hosts (sometimes 45%...). Most of the VMs are configured with 2vCPU and are VMs with little load.
The extrange thing is that I&#039;m seeing 400 or 500 or 600 as values for the %WAIT parameter!!
Is it a bug? I&#039;ve to read this like 40 or 50 or 60% values? May be I &#039;ve to read the %TWAIT or %BWAIT calues insted the %WAIT value?
Or may be it&#039;s correct.
This seems to happen both in ESX 3.0.2 and ESX 3.5.

TIA,
J</description>
		<content:encoded><![CDATA[<p>Thanks Mike and Rich,vary very interesting.<br />
It was exactly what I was supposing. I&#8217;m seeing 20% RDY (average) in my hosts (sometimes 45%&#8230;). Most of the VMs are configured with 2vCPU and are VMs with little load.<br />
The extrange thing is that I&#8217;m seeing 400 or 500 or 600 as values for the %WAIT parameter!!<br />
Is it a bug? I&#8217;ve to read this like 40 or 50 or 60% values? May be I &#8216;ve to read the %TWAIT or %BWAIT calues insted the %WAIT value?<br />
Or may be it&#8217;s correct.<br />
This seems to happen both in ESX 3.0.2 and ESX 3.5.</p>
<p>TIA,<br />
J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike DiPetrillo</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-1395</link>
		<dc:creator>Mike DiPetrillo</dc:creator>
		<pubDate>Fri, 17 Oct 2008 12:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-1395</guid>
		<description>Rich,

It does all come down to comfort level and number of VMs. Obviously if you have 40 VMs on a host and 50% of the time they&#039;re getting blocked from running you have a problem. Of course if those 40 VMs really weren&#039;t doing anything all the time (maybe you have 40 idle print servers or DHCP servers or something) then 50% ready really isn&#039;t a big deal. I too used to say anything over 5% ready is bad. I&#039;ve slowly increased it over time to the 50% threshold. Again, these are my recommendations - not VMware&#039;s. You&#039;ll have to find something that you&#039;re comfortable and as always LOOK and UNDERSTAND your applications. I&#039;ve seen too many customers that have no clue what they&#039;re app is doing or is supposed to be doing and then they want to start troubleshooting at the virtualization layer. Bad idea.</description>
		<content:encoded><![CDATA[<p>Rich,</p>
<p>It does all come down to comfort level and number of VMs. Obviously if you have 40 VMs on a host and 50% of the time they&#8217;re getting blocked from running you have a problem. Of course if those 40 VMs really weren&#8217;t doing anything all the time (maybe you have 40 idle print servers or DHCP servers or something) then 50% ready really isn&#8217;t a big deal. I too used to say anything over 5% ready is bad. I&#8217;ve slowly increased it over time to the 50% threshold. Again, these are my recommendations &#8211; not VMware&#8217;s. You&#8217;ll have to find something that you&#8217;re comfortable and as always LOOK and UNDERSTAND your applications. I&#8217;ve seen too many customers that have no clue what they&#8217;re app is doing or is supposed to be doing and then they want to start troubleshooting at the virtualization layer. Bad idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike DiPetrillo</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-5443</link>
		<dc:creator>Mike DiPetrillo</dc:creator>
		<pubDate>Fri, 17 Oct 2008 12:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-5443</guid>
		<description>Rich,

It does all come down to comfort level and number of VMs. Obviously if you have 40 VMs on a host and 50% of the time they&#039;re getting blocked from running you have a problem. Of course if those 40 VMs really weren&#039;t doing anything all the time (maybe you have 40 idle print servers or DHCP servers or something) then 50% ready really isn&#039;t a big deal. I too used to say anything over 5% ready is bad. I&#039;ve slowly increased it over time to the 50% threshold. Again, these are my recommendations - not VMware&#039;s. You&#039;ll have to find something that you&#039;re comfortable and as always LOOK and UNDERSTAND your applications. I&#039;ve seen too many customers that have no clue what they&#039;re app is doing or is supposed to be doing and then they want to start troubleshooting at the virtualization layer. Bad idea.</description>
		<content:encoded><![CDATA[<p>Rich,</p>
<p>It does all come down to comfort level and number of VMs. Obviously if you have 40 VMs on a host and 50% of the time they&#8217;re getting blocked from running you have a problem. Of course if those 40 VMs really weren&#8217;t doing anything all the time (maybe you have 40 idle print servers or DHCP servers or something) then 50% ready really isn&#8217;t a big deal. I too used to say anything over 5% ready is bad. I&#8217;ve slowly increased it over time to the 50% threshold. Again, these are my recommendations &#8211; not VMware&#8217;s. You&#8217;ll have to find something that you&#8217;re comfortable and as always LOOK and UNDERSTAND your applications. I&#8217;ve seen too many customers that have no clue what they&#8217;re app is doing or is supposed to be doing and then they want to start troubleshooting at the virtualization layer. Bad idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-1394</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Fri, 17 Oct 2008 12:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-1394</guid>
		<description>Interesting recommendation for %ready times. I&#039;ve always heard / read that double digit ready time was bad (so &gt;10%). As always, it&#039;s relative to the application on each VM and the user experience impact. More on this topic at http://communities.vmware.com/docs/DOC-7390.</description>
		<content:encoded><![CDATA[<p>Interesting recommendation for %ready times. I&#8217;ve always heard / read that double digit ready time was bad (so &gt;10%). As always, it&#8217;s relative to the application on each VM and the user experience impact. More on this topic at <a href="http://communities.vmware.com/docs/DOC-7390" rel="nofollow">http://communities.vmware.com/docs/DOC-7390</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/comment-page-2/#comment-5442</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Fri, 17 Oct 2008 12:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/09/19/deploying-vmware-in-a-linux-shop-po2575/#comment-5442</guid>
		<description>Interesting recommendation for %ready times. I&#039;ve always heard / read that double digit ready time was bad (so &gt;10%). As always, it&#039;s relative to the application on each VM and the user experience impact. More on this topic at http://communities.vmware.com/docs/DOC-7390.</description>
		<content:encoded><![CDATA[<p>Interesting recommendation for %ready times. I&#8217;ve always heard / read that double digit ready time was bad (so &gt;10%). As always, it&#8217;s relative to the application on each VM and the user experience impact. More on this topic at <a href="http://communities.vmware.com/docs/DOC-7390" rel="nofollow">http://communities.vmware.com/docs/DOC-7390</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

