"Not Enough Physical Memory" error

[zabalex]

Any news on the fix?

By the way, I have experienced this error in High Sierra with VMWare Fusion 11.5, I still can't get my VM to run:

[wila]

Hi zabalex,

If your host is running Big Sur then there won't be a fix in Fusion 11.x ...

The solution is to use Fusion 12.

If you are using Fusion 12 for personal use then you can use the free Player (basically Fusion 11 standard), otherwise you'll have to get the upgrade.

edit:

Sorry just realize you are using High Sierra as host OS...

Please be aware that you can't use the very latest Fusion 11.5.5 on that OS, Fusion 11.5 is the last supported version.

See:

https://kb.vmware.com/s/article/2088571

(Sorry for all the edits, seems I'm not awake yet)

Moderator hat on:

Moved to a new discussion as you're not using Big Sur as host OS, making it an entire different issue.

--

Wil

[zabalex]

Thank you for your prompt response and all your edits.

I searched through my old archives and found 11.5.0 which is suppose to be supported by VMWare Fusion for High Sierra. I uninstalled my original version and installed this one. Same result, please help.

I have over 18Gb free on my host, and yet I can't start basic guest OS CentOS.

Anywhere else I could try looking, my env or anything else?

[ColoradoMarmot]

What's the host machine model?

[zabalex]

It is iMac '12,

please let me know if you need additional details.

Thank you so much

[wila]

Not sure why I haven't received any email notifications on this thread? (something broken again on the forums it seems)

Can you attach a vmware.log file from that VM?

Are there other VMs that you can run? (I suppose not, but it is a standard thing to ask)

--

Wil

[zabalex]

Moderator by wila: moved inline text log to attachment.

[zabalex]

Thank you for your reply, again.

To answer your question, no, I can't run any VMs at all. Since about a year ago. Before I had no problem.

[wila]

Hi,

I forgot to tell you, but please attach log files instead of copying the text into the reply as that makes the thread very hard to follow & navigate.

FWIW I moved it to an attachment on your behalf.

It's strange that you're bumping into this problem with a High Sierra host.

You have a small chance of being able to work around it by adding the following line to your .vmx file (with the VM shut down)

vmmon.disableHostParameters = "TRUE"

Sadly I have no HS host here at the moment that I can test with myself.

The question is if it is VMware Fusion misbehaving in not being able to allocate sufficient RAM or if it is something else preventing on your host preventing you to allocate that memory.

--

Wil

[zabalex]

Hello Wil,

Thank you so much for sticking with me. Unfortunately, same result.

Attaching an updated log file (Thanks for converting my old response to an attachment).

Anything else I could try, even with a low probability of success?

Regards,

Sasha

[ColoradoMarmot]

Couple of long-shot ideas:

- make sure you're installing and running fusion as an administrator

- try launching fusion immediately after bootup

- try booting into safe mode (hold down left shift key) and seeing if it'll work (this prevents many things from loading, not sure if fusion will work then or not)

[zabalex]

Hello Wil,

I tried running as 'su' user, (which I tried before as well without any difference), but this time I got this strange error. Please see image attached.

Anything you could suggest based on that?

[zabalex]

And, when I tried this command:

sudo "/Applications/VMware Fusion.app/Contents/MacOS/VMware Fusion" "./Windows XP Professional.vmx"

I get the following error message.

[wila]

Hi,

This error is about the application menu that is bundled with VMware Fusion.

Not really relevant for your original problem.

--

Wil

[wila]

Hmm.. not sure what the error about consistent state is about, but your primary issue is the "not enough Physical Memory" one.

In your case I would try the suggestions made by dlhotka.

If none of that helps, maybe you can try open a ticket with vmware?

I'm not sure if you can still do that though as it seems VMware just changed the rules about who is eligible for opening a ticket.

If you can't open a ticket with vmware then you can try uninstall - reboot - install.

With the reboot inbetween to make sure no old kernel modules stay lingering on.

If that still doesn't help I personally would try older versions of VMware Fusion (iterating backwards, one version at a time)

--

Wil

[ColoradoMarmot]

Hmmm.... SU'ing isn't enough, it has to be installed and run as an actual admin (which is the default account type in OSX).

[zabalex]

Hello Dlhotka, Thank you for your contribution.

But how can I be sure that I install as an admin? It does ask me for elevated permissions, I enter my user name and password, same thing as always happens when application puts itself into Applications folder. Is there anything else I can try?

Isn't this step enough?

[ColoradoMarmot]

Look in system preferences/users - the account should be listed as 'admin'.

Did safe booting work?  The other thing that comes to mind is that some other kernel extension is locking up memory.