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

InstantClone fails due to exceeding maximum number of delta disks (67186)

Last Updated: 4/1/2019Categories: TroubleshootingTotal Views: 6883Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

InstantClone operation on Virtual Machine(SourceVM)  which succeeded during previous invocations starts failing with error similar to:

(vmodl.fault.SystemError) {
faultCause = (vim.fault.GenericVmConfigFault) {
faultCause = (vmodl.MethodFault) null,
faultMessage = (vmodl.LocalizableMessage) [
(vmodl.LocalizableMessage) {
key = "msg.migrate.prepare.failed",
arg = <unset>,
message = "Unable to prepare migration."
},
(vmodl.LocalizableMessage) {
...
reason = "Unable to prepare migration."
msg = "Unable to prepare migration."
},
...
reason = "Launch failure"

In the SourceVM, you see warning alert similar to:

This virtual machine has more than 100 redo logs in a single branch of its snapshot tree. Deleting some of the snapshots or consolidating the redo logs will improve performance.

Cause

This issue is caused due to a limitation of vSphere's delta disks (redo logs). The maximum number of redo log levels supported for a virtual disk is 255. When InstantClone is invoked on a SourceVM, a new delta disk is created for both the SourceVM and the GeneratedVM. These delta disks are not tied to snapshots, so they are not visible via the vSphere UI. At the moment, the only way to examine the presence of these delta disks is via the VM's FileLayoutEx API call or via examining the vmfolder of the SourceVM.
If numerous InstantClone operations are invoked against the same SourceVM, the delta disk chain will increase with each invocation. Once this number reaches 255, InstantClone operation will start failing.

Resolution

To resolve this issue:

Freeze the SourceVM:

The InstantCloneFreeze functionality can be used on the SourceVM to limit the number of new redo log delta disks created for the SourceVM to 1, regardless of the number of InstantClone operations invoked on the SourceVM. See Freezing the Source Virtual Machine for an Instant Clone Operation.

Note: Once a SourceVM is frozen, the VM will still be shown as PoweredOn and running, even though guest instructions are not running. There are no indicators on the vSphere UI to indicate a VM is instantCloneFrozen. The VIM API boolean Vim.VirtualMachine.runtime.instantCloneFrozen can be used to check if a SourceVM is instantCloneForzen. The only way to exit the instantCloneFrozen mode is to powerOff or reset the VM.

Cleanup existing redo log delta disks from SourceVM:

If a Virtual Machine is observed to have a large number of redo log delta disks, invoke the Vim.VirtualMachine.PromoteDisk(unlink=True), which will result in the VM from having a single flat vmdk file.

Clone with memory snapshot as an alternative to InstantClone:

If InstantCloneFreezing is not an option (eg. OS does not have vmtools available), then the Clone with memory snapshots may be used as an alternative way to achieve a very similar end result as InstantClone, with the downside that it will be slower and less memory efficient due to lack of memory page sharing.

By default, the Clone operation will attempt do a full disk copy from the SourceVM to the ClonedVM. To achieve better disk efficiency as well as Clone time, ensure there exists at least one snapshot on the SourceVM, and Clone with diskMoveType=moveChildMostDiskBacking, which will only perform a copy of the SourceVM's latest snapshot rather than the entire disk content.

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 Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant