Solved: Re: 10.10.2 and Fusion pro 7.1.0 superslow

perjoh · ‎01-30-2015

Hello

I have the a problem with a MacBook Pro (Retina, 15-inch, Early 2013) 10.10.2 and Fusion pro 7.1.0.

The problems started after i upgraded to 10.10.2 and the windows 7 that run on fusion i slow and some times stop responding.

Someone that have any ide what to do ?

rgds/Per

hamgva · ‎02-05-2015

The workaround of killing file sharing between Mac and Windows works, but defeats the real reason I bought Fusion in the first place. I have several files that need to be accessed by apps from both environments. At least I can get to Windows though. Hoping fro a complete fix soon.

View solution in original post

Pistouille · ‎01-30-2015

Hi,

Experiencing same problem.

Found a sort of workaround by disabling all folder share mirroring between Host & VM, and back now to normal speed.

It seems to be linked with desktop share between VM and Host, but no further indication now.

Try and let me know if that helps

Rgrds

michaelclach · ‎01-31-2015

Same problem here. I've tried with a few virtual machines and all have the same problem.

aamld · ‎01-31-2015

Same issue for me with Win 8.1 Pro after 10.10.2. 2 to 3 minute pauses after login, start button and files. Pre updated Mac on 10.10.1 runs the same VM fine.

dariusd · ‎01-31-2015

Thanks for the post, perjoh.

For others encountering this slowness issue only since updating to OS X 10.10.2, could you please also include your hardware model information, as perjoh has done in this post? The model name is in (Apple menu) > About this Mac..., and the model identifier is in System Information, under Hardware in the left panel, then look for the Model Identifier in the right panel. It'll be something like "MacPro5,1" or "MacBookPro12,1" or "iMac14,1".

Also, when the problem is occurring, suspend or shut down your VM(s) as usual (be patient...), quit Fusion, and immediately launch Terminal and run the following command:

sudo powermetrics -s interrupts

and post the results back here in the thread.

We may need to request more information from you to help isolate the issue.

Thanks,

--

Darius

michaelclach · ‎02-01-2015

I'm using a MacBookPro11,3.

Starts OK, then seems to hang for a bit (I can see this in Activity Monitor), then recovers, and eventually the VM just quits. When I "sudo powermetrics -s interrupts" I get a message that says "[account] is not in is not in the sudoers file. This incident will be reported." which might be because I'm not signed in via an admin account, some anti-virus thing, or something else.

michaelclach · ‎02-01-2015

And if it's worth anything, it seems that when I quit the VMWare app there's still some big processes that keep going. Here's a screen shot from Activity Monitor.

ttabbara · ‎02-01-2015

Hi

I'm having the same issue, but i'm running regular Fusion Version 7.1.0 (2314774)

My virtual machine (Win 7 Ultimate) is basically unusable since I updated to 10.10.2 yesterday. I can't get any of my work done.

Here' s my model info and Terminal command results:

Hardware Overview:

Model Name: MacBook Pro

Model Identifier: MacBookPro10,1

Processor Name: Intel Core i7

Processor Speed: 2.6 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Memory: 16 GB

Boot ROM Version: MBP101.00EE.B07

SMC Version (system): 2.3f36

Machine model: MacBookPro10,1

SMC version: 2.3f36

EFI version: MBP101.00EE.B07

OS version: 14C109

Boot arguments:

Boot time: Sun Feb 1 11:11:19 2015

*** Sampled system activity (Sun Feb 1 11:33:03 2015 -0500) (5000.17ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x46(SMC): 0.80 interrupts/sec

Vector 0x56(HDEF/EHC1): 105.60 interrupts/sec

Vector 0x72(IGPU): 84.00 interrupts/sec

Vector 0x79(ARPT): 12.40 interrupts/sec

Vector 0xdd(TMR): 170.39 interrupts/sec

Vector 0xde(IPI): 32.80 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 1.00 interrupts/sec

Vector 0xde(IPI): 10.20 interrupts/sec

CPU 2:

Vector 0xdd(TMR): 54.00 interrupts/sec

Vector 0xde(IPI): 36.00 interrupts/sec

CPU 3:

Vector 0xdd(TMR): 1.80 interrupts/sec

Vector 0xde(IPI): 19.80 interrupts/sec

CPU 4:

Vector 0xdd(TMR): 69.20 interrupts/sec

Vector 0xde(IPI): 33.20 interrupts/sec

CPU 5:

Vector 0xdd(TMR): 1.60 interrupts/sec

Vector 0xde(IPI): 14.80 interrupts/sec

CPU 6:

Vector 0xdd(TMR): 89.60 interrupts/sec

Vector 0xde(IPI): 30.40 interrupts/sec

CPU 7:

Vector 0xdd(TMR): 1.20 interrupts/sec

Vector 0xde(IPI): 17.20 interrupts/sec

*** Sampled system activity (Sun Feb 1 11:33:08 2015 -0500) (5001.37ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x56(HDEF/EHC1): 67.38 interrupts/sec

Vector 0x72(IGPU): 104.17 interrupts/sec

Vector 0x78(SATA): 0.60 interrupts/sec

Vector 0x79(ARPT): 18.20 interrupts/sec

Vector 0xdd(TMR): 245.93 interrupts/sec

Vector 0xde(IPI): 15.60 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 0.80 interrupts/sec

Vector 0xde(IPI): 5.20 interrupts/sec

CPU 2:

Vector 0xdd(TMR): 37.79 interrupts/sec

Vector 0xde(IPI): 21.19 interrupts/sec

CPU 3:

Vector 0xdd(TMR): 0.80 interrupts/sec

Vector 0xde(IPI): 5.60 interrupts/sec

CPU 4:

Vector 0xdd(TMR): 52.79 interrupts/sec

Vector 0xde(IPI): 20.59 interrupts/sec

CPU 5:

Vector 0xdd(TMR): 0.20 interrupts/sec

Vector 0xde(IPI): 6.00 interrupts/sec

CPU 6:

Vector 0xdd(TMR): 47.79 interrupts/sec

Vector 0xde(IPI): 16.80 interrupts/sec

CPU 7:

Vector 0xdd(TMR): 0.40 interrupts/sec

Vector 0xde(IPI): 7.00 interrupts/sec

*** Sampled system activity (Sun Feb 1 11:33:13 2015 -0500) (5001.15ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x46(SMC): 0.80 interrupts/sec

Vector 0x56(HDEF/EHC1): 112.37 interrupts/sec

Vector 0x72(IGPU): 640.85 interrupts/sec

Vector 0x78(SATA): 0.60 interrupts/sec

Vector 0x79(ARPT): 19.20 interrupts/sec

Vector 0xdd(TMR): 212.15 interrupts/sec

Vector 0xde(IPI): 60.19 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 1.80 interrupts/sec

Vector 0xde(IPI): 20.20 interrupts/sec

CPU 2:

Vector 0xdd(TMR): 64.19 interrupts/sec

Vector 0xde(IPI): 63.19 interrupts/sec

CPU 3:

Vector 0xdd(TMR): 1.00 interrupts/sec

Vector 0xde(IPI): 14.80 interrupts/sec

CPU 4:

Vector 0xdd(TMR): 133.37 interrupts/sec

Vector 0xde(IPI): 62.39 interrupts/sec

CPU 5:

Vector 0xdd(TMR): 1.20 interrupts/sec

Vector 0xde(IPI): 20.80 interrupts/sec

CPU 6:

Vector 0xdd(TMR): 137.37 interrupts/sec

Vector 0xde(IPI): 67.38 interrupts/sec

CPU 7:

Vector 0xdd(TMR): 1.00 interrupts/sec

Vector 0xde(IPI): 15.60 interrupts/sec

*** Sampled system activity (Sun Feb 1 11:33:18 2015 -0500) (5001.32ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x56(HDEF/EHC1): 120.37 interrupts/sec

Vector 0x72(IGPU): 98.77 interrupts/sec

Vector 0x78(SATA): 1.20 interrupts/sec

Vector 0x79(ARPT): 15.80 interrupts/sec

Vector 0xdd(TMR): 268.13 interrupts/sec

Vector 0xde(IPI): 34.59 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 0.60 interrupts/sec

Vector 0xde(IPI): 5.20 interrupts/sec

CPU 2:

Vector 0xdd(TMR): 88.98 interrupts/sec

Vector 0xde(IPI): 36.79 interrupts/sec

CPU 3:

Vector 0xdd(TMR): 0.60 interrupts/sec

Vector 0xde(IPI): 9.80 interrupts/sec

CPU 4:

Vector 0xdd(TMR): 74.38 interrupts/sec

Vector 0xde(IPI): 36.79 interrupts/sec

CPU 5:

Vector 0xdd(TMR): 0.40 interrupts/sec

Vector 0xde(IPI): 7.60 interrupts/sec

CPU 6:

Vector 0xdd(TMR): 88.98 interrupts/sec

Vector 0xde(IPI): 35.59 interrupts/sec

CPU 7:

Vector 0xdd(TMR): 1.00 interrupts/sec

Vector 0xde(IPI): 13.00 interrupts/sec

*** Sampled system activity (Sun Feb 1 11:33:23 2015 -0500) (5001.22ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x46(SMC): 2.40 interrupts/sec

Vector 0x56(HDEF/EHC1): 119.97 interrupts/sec

Vector 0x72(IGPU): 80.78 interrupts/sec

Vector 0x78(SATA): 10.20 interrupts/sec

Vector 0x79(ARPT): 13.20 interrupts/sec

Vector 0xdd(TMR): 262.14 interrupts/sec

Vector 0xde(IPI): 18.20 interrupts/sec

CPU 1:

Vector 0xde(IPI): 1.40 interrupts/sec

CPU 2:

Vector 0xdd(TMR): 52.19 interrupts/sec

Vector 0xde(IPI): 20.99 interrupts/sec

CPU 3:

Vector 0xdd(TMR): 0.20 interrupts/sec

Vector 0xde(IPI): 7.60 interrupts/sec

CPU 4:

Vector 0xdd(TMR): 67.58 interrupts/sec

Vector 0xde(IPI): 22.39 interrupts/sec

CPU 5:

Vector 0xde(IPI): 7.80 interrupts/sec

CPU 6:

Vector 0xdd(TMR): 59.19 interrupts/sec

Vector 0xde(IPI): 25.19 interrupts/sec

CPU 7:

Vector 0xdd(TMR): 0.60 interrupts/sec

Vector 0xde(IPI): 7.00 interrupts/sec

*** Sampled system activity (Sun Feb 1 11:33:28 2015 -0500) (5000.62ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x56(HDEF/EHC1): 34.20 interrupts/sec

Vector 0x72(IGPU): 92.19 interrupts/sec

Vector 0x78(SATA): 0.20 interrupts/sec

Vector 0x79(ARPT): 11.60 interrupts/sec

Vector 0xdd(TMR): 224.17 interrupts/sec

Vector 0xde(IPI): 22.20 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 0.20 interrupts/sec

Vector 0xde(IPI): 3.00 interrupts/sec

CPU 2:

Vector 0xdd(TMR): 46.99 interrupts/sec

Vector 0xde(IPI): 17.40 interrupts/sec

CPU 3:

Vector 0xdd(TMR): 0.20 interrupts/sec

Vector 0xde(IPI): 4.60 interrupts/sec

CPU 4:

Vector 0xdd(TMR): 28.80 interrupts/sec

Vector 0xde(IPI): 15.60 interrupts/sec

CPU 5:

Vector 0xdd(TMR): 0.40 interrupts/sec

Vector 0xde(IPI): 5.00 interrupts/sec

CPU 6:

Vector 0xdd(TMR): 51.99 interrupts/sec

Vector 0xde(IPI): 19.00 interrupts/sec

CPU 7:

Vector 0xdd(TMR): 0.40 interrupts/sec

Vector 0xde(IPI): 7.40 interrupts/sec

hamgva · ‎02-01-2015

Sam problem. Only astride after 12.2.2

MacBookPeo Retina mid 2012

Intel I7

16 gig ram

bgrubbs · ‎02-04-2015

Having the same issues, here are the results with the VM trying to run, but basically having a spinning beachball. VM is a windows 7, Was fine before 10.10.2.

This system doesn't support display of c-state info.

Machine model: MacBook6,1

SMC version: 1.51f53

EFI version: MB61.00C8.B00

OS version: 14C109

Boot arguments: debug=0x10

Boot time: Mon Feb 2 17:42:57 2015

*** Sampled system activity (Wed Feb 4 13:20:05 2015 -0500) (5001.08ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x42(HPET): 219.35 interrupts/sec

Vector 0x52(OHC2/SATA/Z000/LSI0): 92.58 interrupts/sec

Vector 0x56(SBUS/EHC1/LSMB/LUS2): 1.00 interrupts/sec

Vector 0x70(IGPU): 34.99 interrupts/sec

Vector 0x73(ARPT): 47.19 interrupts/sec

Vector 0xdd(TMR): 541.88 interrupts/sec

Vector 0xde(IPI): 373.52 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 572.48 interrupts/sec

Vector 0xde(IPI): 425.71 interrupts/sec

*** Sampled system activity (Wed Feb 4 13:20:10 2015 -0500) (5000.89ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x42(HPET): 287.55 interrupts/sec

Vector 0x52(OHC2/SATA/Z000/LSI0): 88.58 interrupts/sec

Vector 0x56(SBUS/EHC1/LSMB/LUS2): 1.00 interrupts/sec

Vector 0x70(IGPU): 26.40 interrupts/sec

Vector 0x73(ARPT): 20.60 interrupts/sec

Vector 0xdd(TMR): 551.70 interrupts/sec

Vector 0xde(IPI): 405.73 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 400.93 interrupts/sec

Vector 0xde(IPI): 457.92 interrupts/sec

*** Sampled system activity (Wed Feb 4 13:20:15 2015 -0500) (5000.49ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x42(HPET): 300.57 interrupts/sec

Vector 0x52(OHC2/SATA/Z000/LSI0): 190.18 interrupts/sec

Vector 0x56(SBUS/EHC1/LSMB/LUS2): 1.00 interrupts/sec

Vector 0x70(IGPU): 10.20 interrupts/sec

Vector 0x73(ARPT): 20.60 interrupts/sec

Vector 0xdd(TMR): 543.95 interrupts/sec

Vector 0xde(IPI): 505.55 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 323.57 interrupts/sec

Vector 0xde(IPI): 600.74 interrupts/sec

*** Sampled system activity (Wed Feb 4 13:20:20 2015 -0500) (5000.27ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x42(HPET): 274.39 interrupts/sec

Vector 0x52(OHC2/SATA/Z000/LSI0): 56.40 interrupts/sec

Vector 0x56(SBUS/EHC1/LSMB/LUS2): 0.80 interrupts/sec

Vector 0x70(IGPU): 28.40 interrupts/sec

Vector 0x73(ARPT): 49.80 interrupts/sec

Vector 0xdd(TMR): 535.97 interrupts/sec

Vector 0xde(IPI): 323.78 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 485.37 interrupts/sec

Vector 0xde(IPI): 387.18 interrupts/sec

*** Sampled system activity (Wed Feb 4 13:20:25 2015 -0500) (5001.14ms elapsed) ***

**** Interrupt distribution ****

CPU 0:

Vector 0x42(HPET): 227.75 interrupts/sec

Vector 0x51(OHC1/GIGE/LUS0/LMAC): 0.20 interrupts/sec

Vector 0x52(OHC2/SATA/Z000/LSI0): 144.37 interrupts/sec

Vector 0x56(SBUS/EHC1/LSMB/LUS2): 1.00 interrupts/sec

Vector 0x70(IGPU): 33.39 interrupts/sec

Vector 0x73(ARPT): 60.39 interrupts/sec

Vector 0xdd(TMR): 650.25 interrupts/sec

Vector 0xde(IPI): 319.53 interrupts/sec

CPU 1:

Vector 0xdd(TMR): 456.10 interrupts/sec

Vector 0xde(IPI): 404.31 interrupts/sec

bgrubbs · ‎02-05-2015

Turning off mirroring of the documents folder eliminated the performance issues for me as well.

HPReg · ‎02-05-2015

There are two known "slow VM" issues :

1) The first only happened on iMac, affected all virtualization products, and was caused by an interrupt storm (to check for it, we recommended people run the "sudo powermetrics -s interrupts" command). This issue was tracked by the thread Fusion 7 is running VERY SLOW on the GM of Yosemite . It was an Apple bug that Apple has solved in Yosemite 10.10.2.

2) The second only happens with Fusion VMs, and started to happen with Yosemite 10.10.2. It is tracked by this thread. It is being investigated by VMware. As reported by mjhd , in the meantime the workaround is to turn off the Settings > Sharing > Mirrored Folders > Desktop checkbox.

[Edited to credit mjhd.]

[Edited to clarify that issue #2 is not specific to Windows VMs.]

mjhd · ‎02-05-2015

Hi,

could you (VMWARE) please provide a working solution for number 2?

this is frustrating to have to do the debugging after buying the license for a premium rate.

PS, it is not ok, to use other reported details without credit.

regards,

hamgva · ‎02-05-2015

The workaround of killing file sharing between Mac and Windows works, but defeats the real reason I bought Fusion in the first place. I have several files that need to be accessed by apps from both environments. At least I can get to Windows though. Hoping fro a complete fix soon.

HPReg · ‎02-05-2015

> could you (VMWARE) please provide a working solution for number 2?

We are working on it.

> this is frustrating to have to do the debugging after buying the license for a premium rate.

Note that nobody could do the debugging earlier: Fusion 7.1 was released Dec 01, 2014 and Yosemite 10.10.2 was released Jan 28, 2015. VMware does not have a time machine to jump into the future, so when we wrote Fusion 7.1 there was no way for us to anticipate that Apple would break our app when they would release Yosemite 10.10.2 later.

> PS, it is not ok, to use other reported details without credit.

Sorry about that. I'll edit my message to credit you.

mjhd · ‎02-05-2015

Hi HPReg,

I do completely understand your standpoint, I only reply for the seek of better understanding:

did I or any customer force VMware te declare Fusion 7 compatible with Mac OS Yosemite?

VMware is taking big risk releasing a new release upfront of any official OS release.

"testing can be used to show the presence of bugs, but never to show their absence!"

Edsger Dijkstra

Peace and Regards,

dariusd · ‎02-05-2015

The issue discussed in this thread is a compatibility problem introduced by the OS X 10.10.2 update. It did not exist in OS X 10.10.0 or OS X 10.10.1.

If we don't declare support for an OS due to the risk of a future (post-release) update breaking things, we would only be able to declare compatibility until after the OS's final update is released – i.e. when the OS vendor is no longer supporting it. In that case, we would have recently declared support for OS X 10.8, and not yet be declaring support for OS X 10.9...

Compatibility issues are a part of life with complex software systems, particularly when many vendors are involved. We try hard to avoid the possibility of such issues, but when they happen in released and supported software, we do what we can to resolve them.

Thanks for your patience,

--

Darius

dariusd · ‎02-05-2015

More questions for the folks affected by this performance issue (or hang) after updating a host to OS X 10.10.2:

1) All the reports so far have been on MacBook/MacBookPro systems, none from desktop (iMac/MacPro/Macmini) systems. Has anyone encountered this problem on a desktop system?

2) Are you using Time Machine to back up your Mac? If so, is the Time Machine accessible when the problem is occurring?

3) Are you using DropBox on your Mac? If so, is your DropBox content accessible when the problem is occurring?

4) Are you using iCloud Drive on your Mac? If so, is your iCloud Drive content accessible when the problem is occurring?

Sorry for the seemingly-random and wide-ranging questions... We have not been able to reproduce this problem in-house, and we are still desperately trying to figure out the cause... Your patience and help with this would be greatly appreciated!

Thanks,

--

Darius

GaryMWatson · ‎02-05-2015

I had the same problem on all my Win7 and Win8 VM's including month-old backups after the 10.10.2 update. After a week of troubleshooting, the last few days with a very good VMware support tech, we figured out that it was folder mirroring that was broken. Shared folders works fine, so the work-around for now is to manually add all the folders you need visibility into from the VM into the shared folders list, and uncheck all of the mirrored folders (some say only the desktop matters but I can't confirm that). I was hours away from wiping my Mac and re-loading everything from scratch, and if that didn't work, buying a new laptop, because I have an important business trip Monday. Supposedly the same bug has bitten Parallels, in case you were thinking about jumping ship.

Cheers,

Gary Watson

Imation

michaelclach · ‎02-05-2015

I've only used a MacBook Pro to get this problem. Yes Time Machine, yes Dropbox, yes iCloud Drive, but I haven't tried to access content in DropBox or iCloud Drive when the problem crops up. Will try sometime when I'm back in the office.