<?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: Maximum numbers of Vcpu in single ESX Host</title>
	<atom:link href="http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 16:53:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: craig</title>
		<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/comment-page-1/#comment-599</link>
		<dc:creator>craig</dc:creator>
		<pubDate>Wed, 04 Mar 2009 15:06:57 +0000</pubDate>
		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=916#comment-599</guid>
		<description>actually, if you refer to my comment on this, it does describe that the VMs we run are serving multiple regiosn which contain, ASIA, EURO and NA in same ESX servers. In the case, we could actually allocate more resources to the VM as the production hours for each region is different. Of course is not 1:1 comparison on the Cpu, we only provide to the system which really need it.</description>
		<content:encoded><![CDATA[<p>actually, if you refer to my comment on this, it does describe that the VMs we run are serving multiple regiosn which contain, ASIA, EURO and NA in same ESX servers. In the case, we could actually allocate more resources to the VM as the production hours for each region is different. Of course is not 1:1 comparison on the Cpu, we only provide to the system which really need it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PiroNet</title>
		<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/comment-page-1/#comment-598</link>
		<dc:creator>PiroNet</dc:creator>
		<pubDate>Wed, 04 Mar 2009 14:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=916#comment-598</guid>
		<description>I find the limit OK so far.
What surprised me is your statement: &quot; have most VMs running with 4 Vcpu as the result of customer compare VM to Physical Servers to ensure the performance is sustainable or improve when they switch to VM. &quot;

Mate you must educate your customers, this is not a 1:1 scenario, 1 physical server wit x CPU=1 virtual machine with the same number of vCPU.

Read more about how VMware co-schedules physical processors ...</description>
		<content:encoded><![CDATA[<p>I find the limit OK so far.<br />
What surprised me is your statement: &#8221; have most VMs running with 4 Vcpu as the result of customer compare VM to Physical Servers to ensure the performance is sustainable or improve when they switch to VM. &#8221;</p>
<p>Mate you must educate your customers, this is not a 1:1 scenario, 1 physical server wit x CPU=1 virtual machine with the same number of vCPU.</p>
<p>Read more about how VMware co-schedules physical processors &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: craig</title>
		<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/comment-page-1/#comment-591</link>
		<dc:creator>craig</dc:creator>
		<pubDate>Sun, 01 Mar 2009 04:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=916#comment-591</guid>
		<description>Revise = Max Vcpu in single ESX server to 192</description>
		<content:encoded><![CDATA[<p>Revise = Max Vcpu in single ESX server to 192</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: craig</title>
		<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/comment-page-1/#comment-590</link>
		<dc:creator>craig</dc:creator>
		<pubDate>Sat, 28 Feb 2009 17:07:58 +0000</pubDate>
		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=916#comment-590</guid>
		<description>Hi Duncan, I am little confuse about the max number here, according to the document I downloaded from vmware, it show 128  Vcpu per servers. Not sure is the document error. Maybe you can help to clarify on this.

Personally I have to say that different environment have different way to manage. We serve multiple timezone in single ESX servers, result as the busy hours for each VM will be different as it provide flexibility for my case to allocate more resources without impact the rest of the VM on same host. Just my 2 cents to share</description>
		<content:encoded><![CDATA[<p>Hi Duncan, I am little confuse about the max number here, according to the document I downloaded from vmware, it show 128  Vcpu per servers. Not sure is the document error. Maybe you can help to clarify on this.</p>
<p>Personally I have to say that different environment have different way to manage. We serve multiple timezone in single ESX servers, result as the busy hours for each VM will be different as it provide flexibility for my case to allocate more resources without impact the rest of the VM on same host. Just my 2 cents to share</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/comment-page-1/#comment-588</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Sat, 28 Feb 2009 13:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=916#comment-588</guid>
		<description>If you are currently hitting this max on a non-vdi environment than you need to change your provisioning. By the way the current max is 192 and not 128. And my guess is this will go up considering the fact that 8 vcpu&#039;s will be available in the next version.

again keep in mind that using multiple vcpu vm&#039;s as standard will make scheduling much more difficult.</description>
		<content:encoded><![CDATA[<p>If you are currently hitting this max on a non-vdi environment than you need to change your provisioning. By the way the current max is 192 and not 128. And my guess is this will go up considering the fact that 8 vcpu&#8217;s will be available in the next version.</p>
<p>again keep in mind that using multiple vcpu vm&#8217;s as standard will make scheduling much more difficult.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ratatouille</title>
		<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/comment-page-1/#comment-587</link>
		<dc:creator>ratatouille</dc:creator>
		<pubDate>Sat, 28 Feb 2009 09:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=916#comment-587</guid>
		<description>I guess have to be a little patient hopefully it will be address in the coming release</description>
		<content:encoded><![CDATA[<p>I guess have to be a little patient hopefully it will be address in the coming release</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.306 seconds -->

