I’ve recently dealt with an issue related to snapshot creation and deletion in VMware – specifically, broken snapshot hierarchies. This often happens when a backup solution like NetBackup or Veeam creates multiple snapshots without properly cleaning up the old ones. The result? A growing chain of outdated snapshots that can’t be deleted through the usual GUI method.
Trying to clean them up the standard way (right-click > Delete All Snapshots) failed with this error:
A general system error occurred: Fault cause: vim.fault.GenericVmConfigFault
Finding a Fix
After digging around, I found a few solid blog posts that helped me understand what’s going on:
- Snapshot removal error – A general system error occurred: Fault cause: vim.fault.GenericVmConfigFault – Focus
- VMware View Instant Clones ‘vim.fault.GenericVmConfigFault An error occurred while reverting to a snapshot’ – Insecure Wire
- How to fix “A general system error occurred: vim.fault.GenericVmConfigFault” When creating or Removing Snapshots in VMware – Get-SysadminBlog
I highly recommend checking out those articles. They walk through the problem in detail, and their solutions helped shape the workaround I ended up using.
Word of Caution
Before you proceed, make sure this workaround fits your situation. I’d only be comfortable doing this if:
- The snapshots were created by a backup process.
- You’re confident they don’t contain critical state (i.e., delta files are essentially empty or unused).
Get familiar with your environment and make the right assessment – don’t blindly follow steps unless you’re sure.
The Workaround (Manual Cleanup via SSH)
If you’ve validated your case and are ready to move forward, here’s what worked for me:
- SSH into the ESXi host where the VM is registered.
- Navigate to the VM’s folder, usually under
/vmfs/volumes/datastore_name/VM_Name/ - Create a temp folder:
mkdir tmp - Move snapshot metadata files out of the way:
mv *.vmsd tmp/ mv *.vmsn tmp/
What Happens Next?
After doing this, check the VM in vCenter. You’ll notice all the snapshots are gone from the GUI – like they never existed. Now:
- Right-click the VM > Snapshots > Delete All Snapshots
- This will consolidate the delta
.vmdkfiles on the datastore
Final Cleanup
Once that’s done, go back into the VM folder and verify that no delta .vmdk files are left behind. If there are, and they’re not linked to the running VM, it’s safest to:
- Do a Storage vMotion (migrate storage only) to a different datastore.
- This will move only the active files.
- Any leftover junk (old deltas, snapshot remnants) will be left behind – and can safely be deleted.
Wrap-Up
This workaround saved me in a tight situation. It’s not an official method, but when you’re stuck with a broken snapshot chain and a GenericVmConfigFault, sometimes a little manual cleanup does the trick – just make sure you know what you’re removing.