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

Fully automated DRS places hosts into maintenance mode without taking into account potential resource pool violations (60326)

Last Updated: 1/23/2019Categories: InformationalTotal Views: 6545Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

During patching by vSphere Update Manager or NSX-v host/cluster upgrade, fully automated DRS can select hosts to enter maintenance mode without taking resource pool reservations into account. This could result in VM power-on failures while the upgrade or patching activity is in progress.

Cause

Current vSphere DRS design does not take into consideration resource pool reservations when choosing hosts to be place into maintenance mode.

Impact / Risks

Virtual machines may fail to power on. Although resource pool reservations are not counted, resources of powered on virtual machines are not impacted.

Avoid powering on virtual machines which will have a large demand on resources or which have reservations while the upgrade or patching is ongoing.

Resolution

Currently there is no resolution and is expected behaviour.

Workaround

Ensure the DRS Automation level is set to manual before starting the patching or upgrade process. For NSX upgrades via EAM, one possible workaround is to limit the number of hosts that can be put into MM by using the EAM option.

Procedure

Browse to a cluster in the vSphere Client.

Click the Configure tab and click Services.

Under vSphere DRS click Edit.

Under DRS Automation, select a default automation level for DRS.

Automation Level

Action

Manual

Initial placement: Recommended host is displayed.

Migration: Recommendation is displayed.

Partially Automated

Initial placement: Automatic.

Migration: Recommendation is displayed.

Fully Automated

Initial placement: Automatic.

Migration: Recommendation is run automatically.

Click OK

Note: Do not disable DRS.

When DRS is disabled, the cluster’s resource pool hierarchy and affinity rules are not reestablished when DRS is turned back on. If you disable DRS, the resource pools are removed from the cluster.

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)

Result 1 of 1

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 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant