VMware Communities
JakeRobb
Contributor
Contributor
Jump to solution

"Internal Error" when starting a VM

Hi,

I'm running Fusion 6.0.2 on OS X 10.9.2.  It's a fresh install of 6.0.2 on a machine that was brand new two weeks ago.  My VM is Windows 7 64-bit.  My VM was working before I upgraded to 10.9.2, but I am not sure that's related.  Now, when I start the VM, it quickly fails with a dialog that says "Internal Error."

I found this thread where a few users were having the same symptoms:

Internal Error When starting a VM on Fusion 6 - Mavericks Host

I tried a few of the things listed there, with no luck:

Could you also check $HOME/Library/Logs/VMware/ and $TMPDIR/vmware-$USER for log files of the pattern vmware-vmx-*.log?  If there is none, would you mind doing the following?

- Add the following line to $HOME/LIbrary/Preferences/VMware Fusion/config (please feel free to change the file path to something else)

  vmx.log.temporaryFileName = "/tmp/vmx-temp.log"

- Start the VM.  After the error is observed, attach the file specified above.

There are no files under either path.  I created the config file and added the line, set 777 permissions on both directories, started the VM (it failed again), and checked: STILL no files in either place.

Thank you.  Could you do the following and then try powering on the VM again?

    • Set your core file size limit to unlimited: ulimit -c unlimited
    • In Fusion, go to Settings -> Advanced, and choose "Hang/Crash" for the troubleshooting mode.

Please let me know if the error message changes, and whether there is any core file generated in /cores.

The error message did not change.  I had to force-shutdown my VM to change troubleshooting modes (which was not obvious how to do!).  It did not generate a core file in /cores.

This is intriguing.  Let's try running the VM from the command line.

    • Quit Fusion UI.
    • From a terminal, run
      • sudo /Applications/VMware Fusion.app/Contents/Library/services.sh --start
      • /Applications/VMware Fusion.app/Contents/Library/vmware-vmx-debug -x /Users/kamil/Documents/Virtual Machines.localized/CentOS 64-bit.vmwarevm/CentOS 64-bit.vmx

That would hopefully print out some messages in the terminal that helps us diagnose the issue further.

Starting the service

oke-jrobb-mb:cores jrobb$ sudo /Applications/VMware\ Fusion.app/Contents/Library/services.sh --start

Password:

Installing files from /Library/Preferences/VMware Fusion/thnuclnt

Copying .thnumod to /etc/thnuclnt

Copying thnuclnt.conf to /etc/thnuclnt

Copying thnuclnt.convs to /private/etc/cups

Copying thnuclnt.types to /private/etc/cups

Copying thnucups to /usr/libexec/cups/filter

Restarting printing services

No matching processes were found

Started bridge services

Started network services

Started USB arbitration service

Starting the VM

oke-jrobb-mb:cores jrobb$ /Applications/VMware\ Fusion.app/Contents/Library/vmware-vmx-debug -x /Users/Shared/Windows\ 7\ x64.vmwarevm/Windows\ 7\ x64.vmx

/Applications/VMware Fusion.app/Contents/Library/vmware-vmx-debug is not set-UID root!  <-- is this important?

Attempting a core dump using an unlimited size limit

Core dumped.

A core file is available in "/cores/core.24380"

ASSERT bora/vmx/main/configdb.c:2008

Panic loop

The referenced core file was created.  I compressed it; it's 137MB.  Let me know if you need to see it.

I have attached my Support Information zip file.  Please advise.

Thanks!

Reply
0 Kudos
1 Solution

Accepted Solutions
vvk0110
VMware Employee
VMware Employee
Jump to solution

Have you tried starting the VM after restarting your Mac?

View solution in original post

Reply
0 Kudos
2 Replies
vvk0110
VMware Employee
VMware Employee
Jump to solution

Have you tried starting the VM after restarting your Mac?

Reply
0 Kudos
JakeRobb
Contributor
Contributor
Jump to solution

Sigh.  I thought my days of restarting the computer to resolve issues were behind me.  😕

When I launched Fusion after rebooting, it told me it needed administrator privileges for something.  I entered my password.  Now it works fine.

Thanks.  Smiley Happy

Reply
0 Kudos