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

PercentIdleMBInSpaceDemand option fails to prevent over-provisioning on the Datastore Cluster in VMware vSphere (78833)

Last Updated: 8/4/2021Categories: TroubleshootingTotal Views: 3651Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

PercentIdleMBInSpaceDemand option fails to prevent over-provisioning on the Datastore Cluster in VMware vSphere

VMware Storage DRS is giving incorrect initial placement recommendations.

Cause

This issue occurs due to the the space demand calculation in the VMware Storage DRS algorithm for initial placement does not correctly account for the PercentIdleMBInSpaceDemand parameter in VMware vSphere

Resolution

This is expected behavior for initial placement case. Because, for initial placement, SDRS uses the "used space" of the datastore for generating the recommendation rather than "entitled space". However, SDRS uses the "entitled space" ONLY during load balance.

Example :

Datastore-1 : 50GB Capacity

VM1 - 50GB Thick VM

Used Space - 50GB

Entitled Space - 50GB

Datastore-2 : 50GB Capacity

VM2 - 30GB Thick VM

VM3 - 15GB Thin VM

Used Space - 30GB

Entitled Space - 45GB (Because PercentIdleMBInSpaceDemand is set to 100)

When we create a new VM or add a new disk of size 10GB. SDRS considers the datastore "used space" for initial placement cases. Hence, it will see that only 30GB is used on the Datastore-2. So, it can fit in the new 10GB disk/VM. So, it generates the recommendation.

If we consider entitlement to determine initial placement, some provisioning failures may be undesirable to customers. Specially in a heavily thin provisioning environment when datastore usages are reaching threshold. The headroom part in entitlement can be too conservative.

SDRS considers the space usage of powered-off VMs as well. Considering space growth for powered-off VMs does not make as much sense as for powered-on VMs.

This is a known issue and engineering team is aware of this.

Related Information

The advanced option "PercentIdleMBInSpaceDemand" was designed to work as explained in the blog.
https://frankdenneman.nl/2012/10/01/avoiding-vmdk-level-over-commitment-while-using-thin-disks-and-storage-drs/

By setting the percentage to 100%, no over-commitment will be allowed on the datastore, however the efficiency advantage of using thin disks remains. Storage DRS uses the allocated space to calculate the risk and the cost of a migration recommendation when a datastore avoids its I/O or space utilization threshold.

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)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

VMware vCenter Server 5.5.x

Take Our Survey

Support Assistant