VMware Fusion “Internal Error” and how to correct it!

June 27th, 2011
by Christopher Kusek (PKGuild)

If you’re like me, all of a sudden you’re getting an “Internal Error” and you’re like WTF?! IT WAS WORKING A MINUTE AGO! AHHHHHHHH!!!    And you go through the normal course of action of googling for answers only to find each and every scenario doesn’t apply to you [Heck, you even DO what they suggest and it still doesn’t work!]   Well, hopefully this finds you in good tidings and will solve your problem fast and furious!

Disclaimer: I try to quantify the scenario which leads up to this particular version of the error and a quick and hearty resolution.  If your situation does not meet this particular criteria.. you may want to go back to searching and trying the other options! Unfortunately, this has hit me too many times for me to let it go unpublished! :)

As with most things, I try to be as SPECIFIC as possible so you can get to the point and solve (even with this verbose dialogue ;))

Standard Operation

There you are, just sitting along using VMware Fusion with whatever your VM type happens to be, and then either you close the lid on your mac, or your VM starts to suspend itself [Or you manually suspend it, doesn’t matter]   But wait.   The VM gets to 99% or so, but never officially ends/closes/suspends.   You cannot “resume” a VM which thinks it is still suspending, so you’re forced to do the following:

Killing VMware Fusion

Activity Monitor: Find your VMware Fusion instance and Force Quit the ProcessAre you sure you want to quit this Process? The Process of killing the VMware Fusion running instance.VMware Quit unexpectedly when Force Quitting the process in VMware Fusion

Well, that seemed straightforward enough! Wham BAM! Process Killed, am I right?! [No. I’m not right ;)]

Internal Error

   You re-launch VMware Fusion, go to open up your VM and OMG IM GETTING INTERNAL ERROR WTF IS GOING ON HERE!

Some of you, first action you’ll take is to go into the VMware Fusion Package and start to remove .LCK files and everything under the sun because you’re panicked! AHHH PANIC!   Well, panic no longer!   There is hope!

What causes Internal Error

If you open up Terminal and take a look at your /var/log/system.log you’ll find the following is happening {cat /var/log/system.log}

Jun 24 12:15:29 CXI [0x0-0x86e86e].com.vmware.fusion[47446]: VMware Fusion Error:
Jun 24 12:15:29 CXI [0x0-0x86e86e].com.vmware.fusion[47446]: Failed to get exclusive lock on the configuration file. Another VMware process might be running using this configuration file.

Recovering from Internal Error

There are two quick ways to get out of this.   One is a reboot [lame!] And the other is to kill the running instance using kill

Use PS to find the process in question [ps –axwww | grep vmware]

Then use Kill to kill the process in question! [kill –9 ProcessID]


Hopefully you found this useful and if not… I’m sure I’ll run into this situation AGAIN and forget how I solved it, and come back to this blog post of my own in order to correctify the situation! :)  If you find this useful at all, let me know so I can gauge just how many of us experience this kind of pain :)

Take care and Good Luck! :)

Tags: , , , , , , ,
Posted in vmware, VMware Fusion | Comments (17)

  • Bas Raayman says:

    After @CXI:twitter gave me a friendly hint on Twitter, I thought I might as well post the error message I got in Fusion. The error was “Cannot find valid peer process to connect to”, and in the end killing all of the processes (or a simple reboot) will also help. And if that alone doesn’t do the trick, follow the steps outlined in this VMware KB article and then reboot the machine: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1018757 :)

  • magu says:

    You, sir, are a legend!

  • Tim W says:

    Thank you for this post! It totally resolved the error message issue I was recently experiencing in VMWare! Cheers :D

  • Neil says:

    You say kill the process in question, but I have no idea which process is causing the problem.  I get this
    Bon-Air-Mac-Pro:~ neil$ ps -axwww | grep vmware  115 ??         0:00.11 /Library/Application Support/VMware Fusion/vmnet-dhcpd -s 6 -cf /Library/Application Support/VMware Fusion/vmnet1/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet1.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1  119 ??         0:00.11 /Library/Application Support/VMware Fusion/vmnet-dhcpd -s 6 -cf /Library/Application Support/VMware Fusion/vmnet8/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet8.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet813762 ??         6:40.77 /Library/Application Support/VMware Fusion/vmware-vmx -E en -D FGCFI7aPK/YPcwAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= -s vmx.stdio.keep=TRUE -# product=1;name=VMware Fusion;version=3.1.3;buildnumber=416484;licensename=VMware Fusion for Mac OS;licenseversion=3.0+; -@ pipe=/var/folders/bc/bcxjY7c7Fa8w2jpzFOgeMk+++TQ/-Tmp-//vmware-neil/vmx1267da6ba013376e;readyEvent=34 /Volumes/Data Folders/Virtual Machines.localized/FreeBSD/freebsd.vmx13942 ??         0:00.05 /Library/Application Support/VMware Fusion/vmware-usbArbitratorTool /Volumes/User Folders/Users/neil/Library/Logs/VMware Fusion14048 ??         0:00.05 /Library/Application Support/VMware Fusion/vmware-usbArbitratorTool /Volumes/User Folders/Users/neil/Library/Logs/VMware Fusion14073 ??         0:00.44 /Library/Application Support/VMware Fusion/vmware-vmx -E en -D H2sWpOyuJcEPcwAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= -s vmx.stdio.keep=TRUE -# product=1;name=VMware Fusion;version=3.1.3;buildnumber=416484;licensename=VMware Fusion for Mac OS;licenseversion=3.0+; -@ pipe=/var/folders/bc/bcxjY7c7Fa8w2jpzFOgeMk+++TQ/-Tmp-//vmware-neil/vmx5e1982f97c3ceb20;readyEvent=36 /Volumes/Data Folders/Virtual Machines.localized/Windows XP Professional copy.vmwarevm/Windows XP Professional.vmx14096 ??         0:00.39 /Library/Application Support/VMware Fusion/vmware-vmx -E en -D H2sWpOyuJcEPcwAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= -s vmx.stdio.keep=TRUE -# product=1;name=VMware Fusion;version=3.1.3;buildnumber=416484;licensename=VMware Fusion for Mac OS;licenseversion=3.0+; -@ pipe=/var/folders/bc/bcxjY7c7Fa8w2jpzFOgeMk+++TQ/-Tmp-//vmware-neil/vmx9a391a1b28ea980c;readyEvent=35 /Volumes/Data Folders/Virtual Machines.localized/Windows XP Professional copy 2.vmwarevm/Windows XP Professional.vmx14163 ??         0:00.05 /Library/Application Support/VMware Fusion/vmware-usbArbitratorTool /Volumes/User Folders/Users/bonair/Library/Logs/VMware Fusion14181 ??         0:00.46 /Library/Application Support/VMware Fusion/vmware-vmx -E en -D grKWI644FHEDPwAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= -s vmx.stdio.keep=TRUE -# product=1;name=VMware Fusion;version=3.1.3;buildnumber=416484;licensename=VMware Fusion for Mac OS;licenseversion=3.0+; -@ pipe=/var/folders/Q+/Q+hYQwDqGO0mTL8UThMOe++++TM/-Tmp-//vmware-bonair/vmx6b1ce31d3c807ecd;readyEvent=33 /Volumes/Data Folders/Virtual Machines.localized/Su.vmwarevm/Windows XP Professional.vmx14262 ??         0:00.04 /Library/Application Support/VMware Fusion/vmware-usbArbitratorTool /Volumes/User Folders/Users/bonair/Library/Logs/VMware Fusion14341 ??         0:06.26 /Applications/VMware Fusion.app/Contents/MacOS/vmware -psn_0_217960414349 ??         0:00.04 /Library/Application Support/VMware Fusion/vmware-usbArbitratorTool /Volumes/User Folders/Users/bonair/Library/Logs/VMware Fusion14701 ??         0:00.04 /Library/Application Support/VMware Fusion/vmware-usbArbitratorTool /Volumes/User Folders/Users/neil/Library/Logs/VMware Fusion14928 ttys000    0:00.00 grep vmware

  • Michael Jervis says:

    Worked like a charm

  • Glad to hear it worked for you! :)

  • K Assouline says:

    Thanks a thousand. Merci beaucoup

  • you-are-pwned says:

    Hey, thanks for this, worked perfectly. But I had an another message in the system log:
    Mar 23 12:44:19 mac-mike VMware Fusion 536016[9096]: Error: Unable to start the bridge services. Error: /Applications/VMware Fusion.app/Contents/Library/vmnet-bridge is already running, process ID: 1123 [1]

  • BMacdonald says:

    Thank you!

  •  I take it that was useful then?:)

  • Cdo2003 says:

    All you have to do is

    1 – close the VMware fusion
    2 – delete the .vmem file and others that are created in the time that you are trying to access the VM. WARNING: Do not delete the .VMDK files!!
    3 – open the Vmware fusion again
    4 – Done!
    5 – be happy again!

  • Cmiglian says:

    Olá, muito obrigado!!! funcionou …

  • sarah says:

    Wonderful! :)  worked perfectly, thanks!

  • Lisa says:

    I encounted this while I might haven’t close my macbook properly. And found your approach very useful. Just thanks for your work!

  • Dedi says:

    finally i got my vmware running good… really great tutorial.. thanks a lot my friend…

  • Dedi says:

    Just kill them all… be there done that

  • rmtn says:

    tried it and got an – Operation not permitted – message

    tried it again with sudo and it worked

    hope this helps someone

    thanks a lot

    • Archives