Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESX host settings for environments with up to 80 virtual machines per host in a VMware HA cluster (1012002)

Last Updated: 6/9/2010Categories: Total Views: 29986Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

Starting with VirtualCenter 2.5 Update 5, an ESX host in an VMware High Availability (HA) cluster can support up to 80 virtual machines. For all virtual machines to power on on other hosts in the cluster if hosts within the failover capacity limit fail, you must ensure that these parameters in the ESX hosts are set with these values:

Parameter

Value

Applicability

Misc.RunningVCpuLimit

192vCPU

ESX Server 3.5 and ESX Server 3i Embedded

Service console memory

512MB

ESX Server 3.5

vim resource pool memory reservation

1024MB

ESX Server 3i Embedded

Host agent memory configuration

<hostdStopMemInMB>380</hostdStopMemInMB>

<hostdWarnMemInMB>300</hostdWarnMemInMB>

ESX Server 3.5 and ESX Server 3i Embedded

Solution

ESX 3.5 Hosts

To enable ESX 3.5 hosts to support up to 80 virtual machines in an HA cluster:

Increase the maximum vCPU limit to 192:

In VMware Infrastructure (VI) Client, select the ESX host.

Click the Configuration tab and select Advanced Settings.

In the Advanced Settings window, select the Misc menu, and change Misc.RunningVCpuLimit to 192.

Include or edit the host agent memory configuration values:

Login to the ESX host as user root using an SSH client.

Make a backup copy of the host agent configuration file /etc/vmware/hostd/config.xml. This backup copy can be placed in the / directory.

Edit the /etc/vmware/hostd/config.xml file.

Within the <config> and </config> tags, include or edit these values:

<hostdStopMemInMB>380</hostdStopMemInMB>
<hostdWarnMemInMB>300</hostdWarnMemInMB>

Save the file and exit.

Note: For the new values to take effect immediately, restart the ESX Server Management service. For more information, see Restarting the Management agents on an ESX or ESXi Server (1003490). If you are going to change the Service Console memory value as described in the next step, rebooting the ESX Server host restarts the ESX Server Management service.

Increase the Service Console memory value to 512 MB:

In VI Client, select the ESX host.

Click the Configuration tab and select Memory.

Click Properties, and in the Memory window, change the value for Service Console to 512.

Reboot the ESX host for the new value to take effect. For more information, see Increasing the amount of RAM assigned to the ESX Server service console (1003501) and Rebooting an ESX Server host (1003530)

ESXi 3 Embedded Hosts

To enable ESXi 3i Embedded hosts to support up to 80 virtual machines in an HA cluster:

Increase the maximum vCPU limit to 192:

In VI Client, select the ESXi host.

Click the Configuration tab and select Advanced Settings.

In the Advanced Settings window, select the Misc menu, and change Misc.RunningVCpuLimit to 192.

Increase the memory resource reservation of the vim resource pool to 1024 MB:

In VI Client, select the ESXi host.

Click the Configuration tab and select System Resource Allocation.

Click Advanced, and select vim from the System Resource Pools list.

Click Edit Settings.

In the Edit vim Resource Allocation window, change the value for Memory Resources Reservation to 1024.

Include or edit the host agent memory configuration values:

Login to the ESXi host using Tech Support Mode as detailed in Tech Support Mode for Emergency Support (1003677)

Make a backup copy of the host agent configuration file /etc/vmware/hostd/config.xml. This backup copy can be placed in the / directory.

Edit /etc/vmware/hostd/config.xml file.

Within the <config> and </config> tags, include/edit these values:

<hostdStopMemInMB>380</hostdStopMemInMB>
<hostdWarnMemInMB>300</hostdWarnMemInMB>

Save the file and exit.

Exit Tech Support Mode

For the changes to take effect, restart the Management Agents on ESXi 3 as described in Restarting the Management agents on an ESX or ESXi Server (1003490)

Note: The Maximum number of hosts per HA cluster is 32 as per the Configuration Maximums for VMware Infrastructure 3 guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

Take Our Survey

Support Assistant