Odd Problem With Vmware Fusion And 10.10.2

Gary Watson

Registered
Right after last week's OSX update, my VMware Fusion started giving me a beachball every few mouse clicks, sometimes locking up for many minutes. I tried my Win 7 and Win 8 VMs and their backups, and all have pretty much the same issue. I tried a manual un-install of Fusion and all its files, then re-install, with no change. VMware spent 3 hours logged into my machine and couldn't figure it out (seemed to be a pretty junior tech, though). Anyway, looking at the Mac system.log file I get a lot of crapola that's synched with the pinweels, which makes it look like it's trying to resolve some external DNS link. I don't think it should be doing that since I don't use external file shares. I emptied the startup menu, and have deleted everything on the Mac and Windows side that is non-essential, just in case. No difference. Turning WiFi on or off makes no difference. Anyway a quick snippet of the log, just wondering if any of you can help me interpret what it's angry about:

Feb 2 11:48:51 Garys-MacBook-Pro.local WindowServer[159]: WSGetSurfaceInWindow : Invalid surface 1214887381 for window 544
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.2 instead of 10.10.2. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: 0 CarbonCore 0x00007fff8eda5d9b ___Gestalt_SystemVersion_block_invoke + 113
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: 1 libdispatch.dylib 0x00007fff8e864c13 _dispatch_client_callout + 8
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: 2 libdispatch.dylib 0x00007fff8e864b26 dispatch_once_f + 117
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: 3 CarbonCore 0x00007fff8ed4e3ca _Gestalt_SystemVersion + 987
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: 4 CarbonCore 0x00007fff8ed4dfb7 Gestalt + 144
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: 5 VMware Fusion 0x000000010c143fe9 _ZN3cui19VMConfigTransaction3SetINS_8vmdevice7USBCtlr12PluginActionEEEvRNS_19TransactionPropertyIT_S0_EERKS6_ + 250041
Feb 2 11:49:15 Garys-MacBook-Pro.local VMware Fusion[1340]: 6 VMware Fusion 0x000000010c17e2e4 _ZN3cui19VMConfigTransaction3SetINS_8vmdevice7USBCtlr12PluginActionEEEvRNS_19TransactionPropertyIT_S0_EERKS6_ + 488372
Feb 2 11:49:20 Garys-MacBook-Pro kernel[0]: fsevents: watcher vmware-vmx (pid: 1485) - Using /dev/fsevents directly is unsupported. Migrate to FSEventsFramework
Feb 2 11:49:50 --- last message repeated 1 time ---
Feb 2 11:49:50 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed
Feb 2 11:49:50 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: ERROR: AFP_GetServerInfo - connect failed 64
Feb 2 11:49:51 Garys-MacBook-Pro kernel[0]: fsevents: watcher vmware-vmx (pid: 1485) - Using /dev/fsevents directly is unsupported. Migrate to FSEventsFramework
Feb 2 11:50:21 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed
Feb 2 11:50:21 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: ERROR: AFP_GetServerInfo - connect failed 64
Feb 2 11:50:49 Garys-MacBook-Pro.local Mail[332]: Stream 0x7fe27978c6f0 is sending an event before being opened
Feb 2 11:50:53 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed
Feb 2 11:50:53 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: ERROR: AFP_GetServerInfo - connect failed 64
Feb 2 11:51:23 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed
Feb 2 11:51:23 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: ERROR: AFP_GetServerInfo - connect failed 64
Feb 2 11:51:54 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed
Feb 2 11:51:54 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: ERROR: AFP_GetServerInfo - connect failed 64
Feb 2 11:52:25 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed
Feb 2 11:52:25 Garys-MacBook-Pro.local NetAuthSysAgent[1498]: ERROR: AFP_GetServerInfo - connect failed 64

Edit: this is the latest OSX, the most recent patches on Win7, Win8, and is the latest VMware Fusion 7. This is a MacBook Pro retina with 16GB of ram and plenty of SSD space.
 
The DNS in the Windows portion needs a DNS manually put it. Use the same time Server for each your Mac and the Windows portion. This should help.
 
The actual problem turned out to be that the 10.10.2 OSX update broke VMware Fusion's folder mirroring capability. The workaround for now is to disable mirroring and use shared folders instead. Root cause may turn out to be related to links to external websites, folders, or files.
 
The actual problem turned out to be that the 10.10.2 OSX update broke VMware Fusion's folder mirroring capability. The workaround for now is to disable mirroring and use shared folders instead. Root cause may turn out to be related to links to external websites, folders, or files.

Report this to Apple at their OS X Feedback web page!

Plus put a report on VMware's VMware Fusion MacUpdate page. They have been known to watch those reviews.
 
Last edited:
It's not exclusive to a particular app like VMware. Those same Console errors occur in other apps too. I recently posted all the nitty gritty details on Apple's forum here:

https://discussions.apple.com/message/27774579

(And no, sadly, I don't know what the solution is, other than perhaps to wait until Apple fixes it in a new update. But it could be a server caching problem.)
 
Back
Top