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

Consolidating snapshots in VMware Workstation (57015)

Last Updated: 1/17/2019Categories: TroubleshootingTotal Views: 12367Language:
English

13 like this article

Subscribe to get an email
newsletter with new updates

13 people found this helpful Please provide article feedback:

Symptoms

1. When starting a virtual machine, you see one of these warnings:

VMware has paused this virtual machine because the disk on which the virtual machine is stored is almost full. To continue, free up at least [X] GB of disk space.

This virtual machine has more than 100 snapshots in a single branch of its snapshot tree. If you take more snapshots of this virtual machine in this branch, the guest operating system may not boot again. You should either delete some snapshots or make a full clone of the virtual machine.

2. When deleting snapshots, you see the warning:

Unable to clean up deleted files. There is not enough space on the file system for the selected operation.

3. You cannot see all of your snapshots in the Snapshots Manager.

4. VMware Workstation says that your virtual disk has snapshots, but you cannot see any.

Resolution

Caution: This article assumes familiarity with how snapshots work.

The most likely reason for running out of disk space (if you have not recently saved any large files to your computer) is that one or more snapshots have grown too large. If this occurs, you have three options:

Make more space.

Automatically consolidate snapshots

Manually consolidate your snapshots

Option 1: Automatically consolidate snapshots

1. Shut down the virtual machine
2. Go to the option 'VM' > Snapshot Manager
3. Select each snapshot and delete them from left-to-right

This consolidates all of your snapshots into your main disk. If you do not have enough disk space to do this, use option 2.

Option 2: Manually consolidate snapshots

If you cannot see any or all of your snapshots in the Snapshot Manager, and you do not have sufficient disk space for Fusion to consolidate them, you must consolidate your snapshots manually.

To consolidate data from the snapshot(s) and from the main virtual disk, use the command-line utility vmware-vdiskmanager to create a new virtual disk.

1. Shut down the virtual machine.
2. Quit VMware Workstation.
3. Open Windows Explorer and locate the virtual machine.
4. Open Command Prompt as an Administrator.
5. Copy and paste this text into Command Prompt:

"C:\Program Files (x86)\VMware\VMware Workstation\vmware-vdiskmanager.exe" -r

6. Give a space.
7. From your virtual machine folder, drag the current virtual disk file into the Command Prompt window.
8. Give a space
9. Copy and paste this text into Command Prompt:

-t 0

10. Give a space
11. Type the new location for the virtual disk, followed by a forward slash ( /), and enter a new file name (for example : NewDisk.vmdk).

Example:

"C:\Users\username\Desktop\NewDisk.vmdk"

12. The command will look similar to this:

"C:\Program Files (x86)\username\VMware Workstation\vmware-vdiskmanager.exe" -r "D:\Virtual Machines\Windows 7\Windows 7.vmdk" -t 0 "C:\Users\username\Desktop\NewDisk.vmdk"

13. Press Enter

14. A message that says Converting... followed by a percentage appears. The length of the process varies depending on the size of the virtual machine.

You may then create a new virtual machine based on this 'NewDisk.vmdk" file

Pointing the virtual machine to the new file

After the snapshots have been consolidated, you need to use the new virtual disk. The easiest way to do this is to make a new virtual machine that uses the new virtual disk you have just created (which has all of the information from your old virtual disk and all of the snapshots). To make a new virtual machine that uses the new virtual disk, refer to Creating a Workstation virtual machine using existing VMDK virtual disks (2010196)

Running a final check

After powering on the new virtual machine, compare it with the old virtual machine and ensure that nothing is missing. If you see any files or folders missing, you may have neglected to re-enable Shared Folders or Mirrored Folders.

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workstation Pro

Related Versions:

VMware Workstation Pro 15.x (Windows)

VMware Workstation Pro 14.x (for Windows)

Take Our Survey

Support Assistant