Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Fusion VM will not start (Memory issues) after upgrading to Maverick

MacBook Air

OSX 10.9

VMWare Fusion 6.01


After upgrading to Maverick my VM will not start anymore.


The error is:


Not enough physical memory is available to power on this virtual machine with its configured settings.

To fix this problem, decrease the memory size of this virtual machine to 744 MB.

It is possible that native applications and/or services have locked down memory which could be preventing the virtual machine from launching. Shutting down unnecessary applications or services may free enough memory to launch this virtual machine.

If you were able to power on this virtual machine on this host computer in the past, try rebooting the host computer. Rebooting may allow you to use slightly more host memory to run virtual machines.


The issues seem to be related to the new memory management.


Is there a workaround or how can this issue be addressed?


TIA

MacBook Air (13-inch Mid 2011), OS X Mavericks (10.9)

Posted on Oct 23, 2013 3:26 AM

Reply
26 replies

Oct 23, 2013 9:35 AM in response to khschulz

I am having the same issue. I was allocating 2048 and it has forced me to drop it to 1024 to work.


I am having periodic success by closing EVERY OS X app and restaring then the VM will start again.


The hilarious part is in the Keynote all they could do is tout how Mavericks uses less memory.


I am on VMware Fusion Version 6.0.1 (1331545)

and

MacBook Air 1.8 Ghz Core i7

Memory 4GB 1333 MHz DDR3

OX 10.9 (13A603)

Oct 23, 2013 9:43 AM in response to dcassidy

In fareness, Mavericks does use less memory - look at how often Mavericks needs to swap to disk (or SSD) and contrast with Mountain Lion or earlier. It's a genuinely impressive trick, and for everything other than VMWare Fusion, it's like having an additional 2GB for free. That's my experience - yours may vary.

The problem, as far as I can see it, is that VMWare needs memory without the jiggery pokery - it is, after all, giving it to another OS. Mavericks doesn't know that VMWare really needs other tasks to be swapped out, and swapped out now, so it diligently does all it can not to swap to disk. Result? VMWare throws a wobbler and refuses to start.

The fix, as I see it, is either for VMWare to release a version of Fusion that isn't so diligent about checking for physical memory on start - once started I think that it will be in a position to muscle Mavericks into swapping to disk any other tasks that are executing (just a theory, I haven't tried this).

The other option would be an update to Mavericks to provide a checkbox in the application info window (for any app, not just VMWare). When ticked, Mavericks would swap out everything that it can in order to allocate RAM to whatever memory hungry app is loading.

Don't shoot Apple over this. In Mavericks they've worked a memory freeing miracle - it might take the developers a little while to catch up.

Oct 24, 2013 1:11 PM in response to khschulz

Okay, the solution seems to be this (it works for me anyway, I hope that it works for you all too).

  1. Find the VMWare Fusion 6 executable (usually in your Applications folder)
  2. Right click on it, and select 'Get Info'
  3. In the VMWare Fusion Info window that opens, click the 'Prevent App Nap' checkbox.
  4. Close the Information Window
  5. Start VMWare Fusion (with your fingers crossed, and touching wood of course.)
  6. Hopefully it will now work.

Please let me know if this works okay for you too.

Fusion VM will not start (Memory issues) after upgrading to Maverick

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.