ESXi VMware vSphere

How to fix “A general system error occurred: vim.fault.GenericVmConfigFault” When creating or Removing Snapshots in VMware.

Recently I had a bunch of virtual machines that started generating this error during Veeam backups. I hadn’t bothered to really be checking my snaps because my daily job was supposed to be taking care of that for me. Unfortunately, this bit me and Here we are

As many of you have probably experienced, Veeam doesn’t always clean up after itself when it is finished backing up a VM. Sometimes a file lock or other operation prevents the snap cleanup, and you end up with a huge chain of snapshots.

Normally you would just be able to right click the VM, select Snapshots, then “delete all” and be done, however I was getting.

A general system error occurred: vim.fault.GenericVmConfigFaultScreen Shot 2017-04-21 at 1.40.54 PM

So how do we fix this? Well it turns out there are two ways.

Resolution 1:

This resolution requires downtime, however is significantly faster. It does however have some caveats I will get to later.

  1. Shut down the Virtual Machine.
  2. SSH to the host where the VM was running.
  3. Change Directory to the volume where the guests disks are stored.
    cd /vmfs/volumes/volumguid/machinefolder
  4. Find all delta.vmdk for the VM
    ls -ltrh | grep delta.vmdk
  5. If it looks something like this you’re good to go. Notice how of the 5 snapshot deltas, only actually has data, the others are empty?
    Screen Shot 2017-04-21 at 1.48.54 PM
  6. If it looks like this, you’re going to have to use Resolution 2. Notice how multiple of the snapshot deltas hold data?
    Screen Shot 2017-04-21 at 1.51.07 PM
  7. Create a new folder in the VMs folder.
    mkdir ./tmp
  8. Move all of the EMPTY snapshot data to the /tmp folder. DO NOT DELETE IT. If the remaining steps do not work we have to restore these files.
    mv VM_1-000001* ./tmp
  9.  Once all Snapshots are moved, and you are left with your base disk and your last snapshot. Open VMware vSphere Client, and create a new VM. Make it identical to the old VM, however DO NOT add a disk. Remove the disk VMware wants to create, and select “add existing disk” Select the snapshot disk, NOT the base disk, and attach it to the VM. Do not select “Power On VM after Creation.”
  10. Once creation is complete you will notice that VMware will show “Virtual machine disks need consolidation.” Right click the VM and chose to consolidate the disk. Once consolidation is complete, boot the VM and verify functionality. You should be all set!

Resolution 2:

If your VM is not recoverable with Resolution 1, your alternate resolution is to use the VMware Standalone converter to convert a “Powered On Windows / Linux Machine.” So yes you are doing a P2V migration of a Virtual machine to a new virtual machine.

This isn’t the best solution in the world and its essentially the same as taking / restoring an OS based backup instead of a VM based one, however it allows your VM to be online during the entire operation which could be a consideration for those who have very small maintenance windows and may not be able to do a full consolidation in that window.

Cameron Joyce is a full stack engineer, having experience with all aspects of on premise datacenter, virtualization, disaster recovery, cybersecurity, and Cloud based *aaS technologies. Cameron Joyce has spent more than a decade working in managed services, and brings that experience to his role as a Sr Presales Engineer. Cameron Joyce now shares solutions to problems and new technology overviews through his blog and youtube channels.

%d bloggers like this: