Running MacBookPro 17" w/4g Ram w/ version 10.5.2. Been running 1.1 for WindowsXP for 6 mos w/ no issues. On Sunday nite, after our group windows tech specialist tried (unsuccessfully) to download some trading templates, I found that when I tried to start up Fusion, it got "stuck at restoring virtual machine state"...so I followed a thread in the fusion community and removed the vmware-vmx from the Activity Monitor. Started Fusion again...still stuck at restoring mode. So I decided to download Fusion version 1.1.2......Started Fusion again....still stuck ....when I did a force quit, I got the Unexpected Signal:10. The dialog box asked: "A log file is available in "/users/annettenagatoshi/Documents/VirtualMachines/WindowsXPProfessional.vmwarevm/vmware.log". Please request support and include the contents of the log file. To collect files to submit to VMware support run"/Library/ApplicationSupport/VMwareFusion/vm-support.tool".
I have investigated in various parts of VMware Fusion on my Mac side and I cannot find this log. I would appreciate HELP.
Thank you powervm for responding...,However, I cannot get to Virtual Machine Package...Fusion won't even launch....I cannot access the Virtual Machine Package.....much less get to anything under the Virtual Machine tab on top. Any ideas on what else I can try?
WinXP VM is located at /users/annettenagatoshi/Documents/VirtualMachines/WindowsXPProfessional.vmwarevm/; Right click on same file and select 'Show Package Contents'.
Delete, WindowsXPProfessional.vmss file
Is that file located on the mac or windows side? Cuz I cannot get into the windows side AT ALL!! I've used Fusion for 7 months with no issues....so I can't say I know a lot about it. If the files you are pointing me towards are on the Mac side, could you please give "sort-of Noob" the hierarchy of files to go thru to get to the files you mentioned in your last post? I would really, really appreciate it.....
Thank you! Works perfect. Almost thought I had to reinstall everything. There should be a force reboot function built into Fusion when such errors occur.
powervm = lifesaver.
Deleting the vmss file worked great. I was having a similar problem with beta 2.2...
Thank you so much, powervm! I almost had a panic attack! This step was almost too easy... I definitely agree with that a "hard boot" option should be implemented into the GUI to perform this very task. Thanks again!!
Hi Powervm, I just had the same error pop up (out of the blue! I wasn't even working with the XP VM).
However, there is no .vmss file in the XP VM package...
Any ideas?
Thank you!
Update: after updating from Fusion 2.0 to 2.01, my Vm is up and running again... no issues.
I am going to presume the failure was due to my update of MacOS to 10.5.6... quite possibly this is why 2.01 came out at the same time???
@powervm. Thanks, that was a lifesaver. Worked perfectly for me and I have my VM back.
I got the same error, and removed the file you suggested, but this had no effect...
Any further sugestions?
thanks
[user:username=cbum}, please take a look at this KB: http://kb.vmware.com/kb/1003595
There are a few more files to be removed, and a configuration change to make.
Thanks Stephen.
There happened to be an updater available, applying it solved the issue...
Here is the KB to resolve this problem::
Removing a Fusion virtual machine's suspended state files
Rick Blythe
Social Media Specialist
VMware Inc.