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

VM with vGPU and large amount of memory becomes unresponsive during vmotion (77212)

Last Updated: 7/24/2023Categories: TroubleshootingTotal Views: 6287Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

- vMotion of a VM with a supported vGPU and a large amount of Memory (example 120 GB)
- VM becomes unresponsive at approximately 70% for 45+ seconds depending on active workload on VM
- Ping response time on an impacted VM does increase but does respond.
- vMotion is eventually successful.
- A VM with supported vGPU and a smaller amount of memory (example 8GB) does not experience this problem.
- An error message while trying to migrate VM with high memory (example 130 GB) and vGPU :
"PCI Plugin reported error during migrate checkpoint write for device pciPassthru0"

Cause

VMware is aware of sub-optimal memory pinning performance in certain scenarios like those described above,  and are currently working to improve this in a future release.

Resolution

Currently there is no resolution for this behaviour.
.

Workaround

Currently there is no workaround for this behaviour

If you have VM's with GPU's and a large amount of memory
- migrate the VM during times of low to no workload on the VM.
- If a critical VM and the impact of the stun time would be unacceptable for you, and it is a member of DRS enabled cluster where the automation level is 'Fully Automated' - consider setting a custom automation for this VM to 'Partially Automated'
- Reboot the VM to free the memory buffer.

Related Information

Using vMotion to Migrate vGPU Virtual Machines
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-8FE6A0DA-49E9-472B-815B-D630CF2014AD.html

Set a Custom Automation Level for a Virtual Machine
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-C21C0609-923B-46FB-920C-887F00DBCAB9.html

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
•
vCloud Director テナント ポータルのメイン メニューに vCloud Availability プラグインがない (77180)

KB
•
无法从 Site Recovery Manager Server 检索对: 公差为 30000 毫秒。 (77235)

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 vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server 7.0.3

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant