Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

ESXi host becomes unresponsive due to large resource pool memory reservation (71044)

Last Updated: 8/26/2020Categories: TroubleshootingTotal Views: 28628Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

On ESXi hosts managed by vCenter 6.7.x, if a resource pool has a very large memory reservation, in some cases hosts might run out of reservable memory leading to:

Single or multiple hosts becoming unresponsive

Various host services crashing with core dumps

A host might become unmanageable from vCenter Server

Various log files containing “Out of memory” or “InsufficientMemoryResourcesFault” type of events

Cause

The old DRS algorithm, prior to the vCenter 6.7.0 release, did not reserve more resources than the current VM demand in the resource pool, even if the resource pool is configured with a higher reservation. If there is a spike in VM resource demand, DRS would react only after the next algorithm run. Before that periodic run, VMs might suffer from temporary performance issues even if the resource pool has configured enough reservation.

In vCenter 6.7.x, DRS uses a two-pass algorithm to allocate a resource pool’s reservation to its child VMs. In the first pass, the resource pool reservation is distributed and capped at the VM’s demand, subject to each VM’s fair share. In the second pass, excess reservation is distributed proportionally, capped at the VM’s configured size. Therefore, resource pool reservation is aggressively allocated to its children, giving more buffer to sudden VM demand spikes. For more information on vCenter 6.7.x DRS change, see: DRS Enhancements in vSphere 6.7.

If a resource pool has a very high resource reservation value, there is a chance that it may reserve most host memory, ESXi kernel or agents may not be able to allocate new memory. This causes the above symptoms on the ESXi host. This is a known issue documented in: KB 52500. As mentioned previously, the 2-pass DRS algorithm adds more memory stress to ESXi if a resource pool uses a large memory reservation. Thus, the above symptoms could be more apparent after upgrading vCenter to a 6.7.x release.

Resolution

This is a known issue affecting vCenter Server 6.7

Note: This is not an issue in vCenter 7.0

Workaround

To workaround this issue:

Reduce the resource pool reservation.

Disable vCenter 6.7.x 2-pass memory reservation algorithm through advanced option in vCenter:

Log in to vCenter  with administrative privilages.

Select the cluster object in inventory.

Select configure tab > vSphere DRS.

Click on Edit > Expand Advanced Options > Add.

Under option, enter "CapRpMemReservationAtDemand" with a value of “1.

Note:

Optionally, another advanced option "CapRpCpuReservationAtDemand " could be set to “1” as well to disable the new 2-pass algorithm for CPU resource. Service restart is not required as the added advanced options would take effect automatically at the next DRS algorithm run.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
vRNI 4.2 のバンドルをアップロードした後、シングルクリックのオフライン アップグレードを開始できない (71315)

KB
•
将 CA 签名的 SSL 证书应用于嵌入式 Orchestrator 端口 8283 (71060)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant