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

DRS fails to migrate vGPU enabled VM's automatically (66813)

Last Updated: 7/3/2023Categories: InformationalTotal Views: 8723Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Symptoms

When placing an Esxi host in maintenance mode DRS may fail to automatically migrate VM's that have vGPU enabled.

Under a Cluster's Monitor tab the "vSphere DRS" -> "Recommendations" section may have a VM Migration recommendation for vGPU VMs with a Reason "Destination host is selected for fixing policy/rule violation or its healthy state is better".

Manually vMotioning vGPU enabled VM's is working as expected.

Cause

This is expected behaviour at this time. Per the documentation, DRS will only complete initial placement of a VM with vGPU, but will not automatically load balance:

Using vMotion to Migrate vGPU Virtual Machines (vmware.com)

"DRS supports initial placement of vGPU VMs running vSphere 6.7 Update 1 and later without load balancing support"

Resolution

Starting with vSphere 8.0 U2, DRS can estimate the Stun Time for a given vGPU VM configuration. When the DRS Cluster Advanced Options are set and the Estimated VM Devices Stun Time for a VM is lower than the VM Devices vMotion Stun Time limit, DRS will automate VM migrations.

To enable this functionality, make sure the infrastructure meets the following requirements:

Healthy vSphere Lifecycle Services (see https://kb.vmware.com/s/article/91891)

Configuration of the VM's vGPU devices through the VCenter UI only

Healthy vMotion network (e.g. vMotion NICs setup through https://core.vmware.com/resource/cluster-quickstart)

Then add the following DRS Cluster Advanced Options:

Option: PassthroughDrsAutomation
Value: 1

Option: LBMaxVmotionPerHost
Value: 1

For vGPU VMs with Stun Times exceeding the "vMotion Stun Time Limit" (default 100 seconds), a VI Admin can add the following DRS Cluster Advanced Option:

Option: VmDevicesStunTimeTolerated
Value: <number of seconds, greater than any VM's Estimated Stun Time in the Cluster> (Default 100 seconds)

OR

Modify the "vMotion Stun Time Limit" in the VM's Configuration -> "VM Options" Tab -> "Advanced" Section

For older releases, to resolve the issue please follow the below mentioned points:

For Maintenance Mode evacuations, please refer vGPU Virtual Machine automated migration for Host Maintenance Mode in a DRS Cluster.

If VM placement issues arise, reduce "DRS Automation" to "Partially Automated" please refer Creating a DRS Cluster for more information.

Workaround

To workaround this issue manually migrate vGPU enabled VMs to another host.

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
•
サービス パートナーの FAQ：VMware vSAN での NetApp ONTAP Select のサポート (67037)

KB
•
在 vSphere 6.5 上，vSAN KMS 运行状况检查间歇性失败并显示 SSL 握手超时错误：“QLC_ERR_TIMEOUT_EXPIRED” (67115)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

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 8.0.2

VMware vCenter Server 7.0.x

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant