Hi,
I just reinstalled, reformatted Mac OSX on Mac Mini (late 2012). Installed Vmware Fusion 7 (latest), but I'm having problems with running any virtual machine.
I run "First Aid" on my mac's disk - everything is ok. My File system is: Mac OS Extended (Journaled).
I installed vmware, downloaded Ubuntu iso. Add -> new -> unchecked "Easy Install"... got an error while running.
Same story with windows 7 pro. Add -> new -> install from disc or img -> etc... I didn't install Vmware tools, because they're greyed (but even so, they are not necessary for ubuntu (I think).. so I guess it's not a problem).
I had Vmware running on this machine before the format, I'm not sure what I'm doing wrong. Any suggestions?
Thanks,
W
I have the same exact issue but on Mac OS Sierra Macbook Pro 2015, VMWare Fusion Pro 8.5 trial version.
The 4 VM's I have were all working fine the night before, but today I try to start them and I get "Internal error" and can't start them. I put in alot of hours on these VM's, SLES11, SLES12, Win7 and Windows 10. This is the 2nd time this has happened for no reason. I had no prior crashes or problems, I have no lock files (.lck). I also checked my Disk with the Mac Disk Utility and it is fine.
I see many people with this issue and I have tried all of their solutions. Now I am wondering if I re-do the VM's I will be wasting my time, as this may very well happen again.
Does Apple or Vmware have a solution or know what causes this ?
Thanks,
Bob Perez (bperez@gw.novell.com)
Did you try to start new VM from .iso file? My old vms don't work, but what's really bothers me is, that I reformatted the mac, installed osx from scratch, downloaded .iso from ubuntu website and STILL have this error. So, what's going on? I guess, Vmware should refund me the money. Their product failed completely
Yes, I installed my Vm's from .iso files. I have tried all the solutions that I have googled. Nothing works. I tried to use vfstool to convert the vm, it does not work either.
Hello everybody,
I have the same pain as you. Would be interesting if you have the same socket error in the vmware logs as I
Have look into your logs:
~/Library/Logs/
find here my original post: Recurring error message "Internal Error" under Sierra
regards David
I do have something with a socket too. I attached a log, please have a look
Here is the end of the log:
2016-10-17T21:36:09.828-05:00| VMware Fusion| I120: Internal VMDB error: VMDB failure (-1)
2016-10-17T21:36:10.206-05:00| VMware Fusion| I120: OnVMStateChanged: alive = 0
2016-10-17T21:36:10.206-05:00| VMware Fusion| I120: Setting power state poweredOff
2016-10-17T21:36:10.210-05:00| VMware Fusion| I120: Vix: [140736991368128 foundryVMPowerOps.c:980]: FoundryVMPowerStateChangeCallback: /Users/ww/Documents/Virtual Machines.localized/Ubuntu 64-bit 16.04.1.vmwarevm/Ubuntu 64-bit 16.04.1.vmx, vmx/execState/val = poweredOff.
2016-10-17T21:36:10.698-05:00| VMware Fusion| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2016-10-17T21:36:10.857-05:00| VMware Fusion| I120: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket
2016-10-17T21:36:10.857-05:00| VMware Fusion| I120: SOCKET connect failed, error 2: No such file or directory
2016-10-17T21:36:14.202-05:00| VMware Fusion| I120: VMMgr::CloseVM: closing VM at /vm/#c879006910f21e6e/
2016-10-17T21:36:14.213-05:00| VMware Fusion| I120: VMMgr::OnVMDestroyed: cleaning up after destroyed VM at /vm/#c879006910f21e6e/
Would you mind providing us the support information and upload it to this post?
It would be helpful for us to figure out the problem. Thanks.
You could get it from Fusion menu. Help-->Collect Support Information
Regards,
Amanda
Would you mind providing us the support information and upload it to this post?
It would be helpful for us to figure out the problem. Thanks.
You could get it from Fusion menu. Help-->Collect Support Information
I'm having the same problem, more or less. I was able to run my VMs on Saturday, but today I get "Internal Error" for both of them. I was going to attach my support information, but it is apparently too large. For some reason there's a 994 MB system.log as part of it! Anyway, it can be found at https://dl.dropboxusercontent.com/u/60565698/VMware%20Fusion%20Problem%20Report%202016-10-31%20at%20...
Oh well, I worked out the issue for me. The drive was somehow mounted as read-only, so that was the problem. The error message left a lot to be desired, though!
Hi
I've been dealing with the same thing; for anyone else who is also facing this, can you please tell me what happens if you do this:
cd /Applications/VMware Fusion.app/Contents/MacOS
./VMware\ Fusion
for me, the app launches and I can startup my VMs without any internal error. When I do it by double clicking on the app, I get the usbarbitrator error in the logs and "internal error".
It's a workaround; kind of annoying, but it works.
Brad
I can confirm the exact issue, trying to open Fusion normally results in an internal error 5. Via terminal however it opens. Here’s the terminal output when doing. Where should this be reported to ensure VMware are aware and fix? Thanks.
Nick:Applications Nick$ /Applications/VMware\ Fusion.app/Contents/MacOS/VMware\ Fusion
I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml"
2016-11-17T09:42:21.987| ServiceImpl_Opener: PID 68104
2016-11-17 09:42:22.025 VMware Fusion[68061:1214190] kCFURLVolumeIsAutomountedKey missing for file:///private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/AppTranslocation/19A650A8-3237-4009-9750-6277DEBC7295/: The file “19A650A8-3237-4009-9750-6277DEBC7295” couldn’t be opened because you don’t have permission to view it.
Thank you! Had the same issues with the "Internal Error" and starting it from a terminal worked for me as well.
I hit the same issue and thanks to bradmr giving us his workaround. After troubleshooting the issue, it appears that MacOS Sierra has added extended attributes to the directories. My guess is it was due to gatekeeper locking things down tighter and having to approve to open the app. To resolve the issue I just removed the extended attributes. See Below.
Notice the @ symbol which means extended attrs
Donnies-MacBook-Pro:MacOS donnierobersonjr$ ls -l
total 16256
-rwxr-xr-x@ 1 root wheel 8319008 Nov 2 2015 VMware Fusion
Use xattr -l <file> to view extended attrs
Donnies-MacBook-Pro:MacOS donnierobersonjr$ xattr -l VMware\ Fusion
com.apple.quarantine: 0081;583882a8;Google\x20Chrome;C9F8958F-EF17-47C2-8E7F-D84DAC276D7F
Use xattr to remove extended attrs
Donnies-MacBook-Pro:Applications donnierobersonjr$ sudo xattr -c -r /Applications/VMware\ Fusion.app/
This shouldn't be necessary. Are you installing and running as an administrator account? 'Regular' accounts on OSX can have strange permission issues like this.
I've also seen this when a root password has been set on OSX.
I am using a Admin account. If you notice the extended attrs are com.apple.quarantine which was added by gatekeeper since it was an app downloaded from the internet. In MacOS Sierra gatekeeper became more restrictive and removed the allow run from anywhere. The only way around it is to drop the com.apple.quarantine atters. You can however get the allow run from anywhere back by sudo spctl --master-disable but this is a little overkill in my opinion
I have run into various products with similar permissions issues. If you are absolutely, positively sure that the application is safe, then you can use the terminal to run the "xattr" command to remove the com.apple.quarantine attribute, which bypasses Gatekeeper and allows you to run the app and its embedded applications.
Here are basic instructions:
1. Open the Terminal from a user account with administrator privileges.
2. Type the command "sudo xattr -r -d com.apple.quarantine <path to application>"
Hint 1: The path to the application is case sensitive - it must be exactly correct.
Hint 2: Use a backslash before any spaces in the application name, as shown in the example below.
Example: sudo xattr -r -d com.apple.quarantine /Applications/VMware\ Fusion.app
Understood, but if it's in /Applications it shouldn't trigger the gatekeeper restrictions, so somethings definitely broken.