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

Snapshots Take a Long Time When “Keep Memory” is Enabled (76687)

Last Updated: 3/27/2020Categories: TroubleshootingTotal Views: 14026Language:
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 taking a snapshot with memory, the VM may be unresponsive and the snapshot may take a long time to complete. This is because the ESX host has to dump the VM’s memory to disk.

When looking in the vmware.log file, we will notice that during the snapshot creation something called Lazy CheckPointing is utilized. Lazy CheckPointing is a feature that allows the VM to continue running while the memory is dumped.

Cause

By default mainMem.ioBlockPages is set to 64 pages. Each page is 4k, so 64 would be 256k and 2048 pages would be 8MB. The ioWait is set to 25ms by default. The array will preform differently with different write sizes, so you should test to see what works best for your environment.

Resolution

By increasing the ioBlockPages and decreasing the ioWait values, we can cut down on both the number of iterations and waiting time ( which in turn will decrease the total time to dump the memory to disk).

Add the below parameters based on your environment and load.

mainMem.ioWait
mainMem.ioBlockPages

It should look like below (value can change based on customer environment.

cat test.vmx | grep -i mainMem
mainMem.ioBlockPages = "2048"
mainMem.iowait = "0"

Workaround

There is no workaround, customer can use quiesce snapshot instead.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
许可证升级后，vRA Code Stream 服务在 UI 中不可见 (76642)

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-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 vSphere

Related Versions:

VMware vSphere ESXi 6.5

VMware vSphere 6.7.x

Take Our Survey

Support Assistant