I have searched high and low for an answer to this problem and can't seem to find one.
I was cleaning up a workstation with VMWare Fusion installed and Running Windows Vista x64.
First the Criticals:
VMWare Version: 1.1.1
IMac Core2Duo Running Leopard 10.5.7
The Circumstances:
I was asked to look at the workstation because the Hard Drive was full, it turned out that the user had 31 Snapshots taken of the Virtual Machine.
Using the VMWare utility I selected the old, uneeded snapshots and deleted them.
The process was going to take a while so I left it over night. When I returned in the AM, the IMac had blown a RAM module, so it went to Apple for a week under warranty.
Now that it is back I try to boot the virtual machine and it give missing VMSN errors.
I believe what happened is that it deleted the actual snapshots but not the references to them in the VMDK file. I have attempted to edit the VMDK file manually, but it crashes whenever it is changed.
Virtual Machine Archive Directory Listing:
Jun 13 13:56 Applications
Jun 20 19:59 Windows Vista x64 Edition 2-000001.vmdk
Jul 2 14:44 Windows Vista x64 Edition 2-000002.vmdk
Jun 20 19:43 Windows Vista x64 Edition 2-000005.vmdk
Jan 14 10:35 Windows Vista x64 Edition 2-000013.vmdk
Feb 21 18:09 Windows Vista x64 Edition 2-000015.vmdk
Mar 7 17:48 Windows Vista x64 Edition 2-000016.vmdk
Mar 19 10:44 Windows Vista x64 Edition 2-000017.vmdk
Mar 20 17:04 Windows Vista x64 Edition 2-000018.vmdk
Mar 21 15:52 Windows Vista x64 Edition 2-000019.vmdk
Apr 8 10:39 Windows Vista x64 Edition 2-000020.vmdk
Apr 16 16:16 Windows Vista x64 Edition 2-000021.vmdk
Apr 17 18:01 Windows Vista x64 Edition 2-000022.vmdk
Apr 16 18:02 Windows Vista x64 Edition 2-000023.vmdk
May 20 10:09 Windows Vista x64 Edition 2-000024.vmdk
Jun 3 08:25 Windows Vista x64 Edition 2-000027.vmdk
Jun 20 19:43 Windows Vista x64 Edition 2-000028.vmdk
May 20 10:11 Windows Vista x64 Edition 2-Snapshot27.vmem
May 20 10:11 Windows Vista x64 Edition 2-Snapshot27.vmsn
May 27 15:00 Windows Vista x64 Edition 2-Snapshot28.vmem
Jun 3 08:26 Windows Vista x64 Edition 2-Snapshot29.vmem
Jun 3 08:26 Windows Vista x64 Edition 2-Snapshot29.vmsn
Jun 20 19:43 Windows Vista x64 Edition 2-Snapshot30.vmem
Jun 20 19:43 Windows Vista x64 Edition 2-Snapshot30.vmsn
Jun 13 13:18 Windows Vista x64 Edition 2-Snapshot31.vmem
Jun 20 19:59 Windows Vista x64 Edition 2-Snapshot31.vmsn
Oct 1 2008 Windows Vista x64 Edition 2-Snapshot7.vmem
Jun 20 19:59 Windows Vista x64 Edition 2.nvram
Jul 1 22:05 Windows Vista x64 Edition 2.vmdk
Jul 2 14:37 Windows Vista x64 Edition 2.vmsd
Jul 2 14:35 Windows Vista x64 Edition 2.vmsd.bad
Jul 2 14:44 Windows Vista x64 Edition 2.vmsd.bad2
Jul 2 14:27 Windows Vista x64 Edition 2.vmx
Jul 2 15:13 Windows Vista x64 Edition 2.vmx.lck
Apr 17 18:10 Windows Vista x64 Edition 2.vmxf
2834420 Jul 2 14:27 quicklook-cache.png
231174 Jun 20 15:58 vmware-0.log
209506 Jun 19 13:44 vmware-1.log
209697 Jun 18 13:46 vmware-2.log
365165 Jun 20 20:00 vmware.log
If anybody has any ideas they are very much appreciated.
Thanks,
Michael
Michael,
I think the first recommendation is to upgrade your verson of Fusion (version 2.0.5 is available, as a free upgrade, here: ), but you probably aready knew that.
After you update Fusion, you'll need to upgrade the virtual machine as well.
You should be able to edit the VMX file (virtual machine configuration), but NOT the VMDK file (virtual disk). Do you have a clean copy of the VMDK still? Also can you post a copy of your VMX file?
Thanks,
Stephen