Fusion 6.2, performance died since upgrading to Mavericks. When mac goes to sleep, VM becomes unresponsive.

[PippoFlash]

Hi,

It is years I do all my development work on a Fusion VM with windows.

It all worked perfectly, but since when I upgraded to Mavericks, the VM at the first computer sleep becomes unresponsive and keeps using 110% of Mac processor.

The same exact VM that worked perfectly before upgrading.

- I removed AppNap, no avail.

- The VM doesn't use a swap file.

- Resources are big. I am on a Retina MBPro, 16 Gigs of ram, 8 for mac 8 for the VM, everything on SSD, 2 cores for mac 2 for the VM, windows 7 ultimate 64.

Now, every time I stop working, I have to reboot the VM, since just switching from textpad to calculator can take minutes.

All was working perfectly before I upgraded to mavericks.

Any hints?

Thank you

Filippo

[objectcentral]

I have the same issue - have had it for a long time now.

I've had an open ticket with them on this issue for months and months now.

It has been totally frustrating - they act like it is not a known issue.

And it has been the same thing over and over - update to the lastest revision of Fusion, make a diagnostic dump, send it to them - the repeat and repeat and repeat.

All to no avail. I think they have a permanent problem, and will never solve this issue.

It has made Fusion essentially worthless. And it had worked perfectly for years and years - now - not a usable tool.

Very frustrating.

[ColoradoMarmot]

Are you sleeping the VM before sleeping the machine?  That's always the most stable option.  Keep in mind though, that it will write out 8GB of virtual RAM before actually finishing the VM sleep, so let it finish before sleeping the host.

[wila]

Hello ,

While it might sound like the same issue, I'd say it is similar and adding your voice to a year old similar problem won't help unless the original author comes back with a tip on what to try as what worked for him.

There are many reasons on why your VM might misbehave.

Please open your own topic on this, so that people answering and trying to help do not confuse the separate questions as now happened already.

edit: Please do not forget to add specific details, like what Mac you're using, guest OS, guest OS configuration, etc.. more details here: HOWTO: Ask (and Answer) Questions

--
Wil

[PippoFlash]

It worked for me to change VM settings from 8 Gb of ram to 4.

Now it works seamlessly.