Re: Upgraded to V6 now seeing: "Not enough physica...

dacmp · ‎10-17-2013

I have several VMs running Win 7, each with 1GB memory configured, all running on an 2012 MBA running Mavricks GM release.

Under Fusion 5, I could actually open up to 4 of these VMs at once, and performance was (usually) acceptable.

Under Fusion 6, I can only open 2 -- the third always produces the "Not enough physical memory..." dialog.

Anything I can do about this?

Thanks,

Doug

--

e320_cdi · ‎10-18-2013

I have seen this as well. Same OS, Fusion 6.0.1 Professional, on a MacBook Pro with Retina display. I do have 16GB of RAM, but had several more things going (ESXi, etc.).

dacmp · ‎10-25-2013

Just a follow up for anyone who might be interested -- I opened a support ticket for this issue. At first support wanted to remote desktop to my Air and monitor my system while I used Fusion -- I declined as I doubt this would yield anything useful, and suspect that they've probably got a few systems of their own on which they could test this issue. Support then suggested turning off App Nap for Fusion -- I tested that, it made no difference.

At this point I'm assuming that perhaps this isn't a widespread issue -- if it were I think there'd be a few more posts and support would have some kind of handle on it -- though I'm surprised that e32_cdi would see something similar on MBP w/16GB. If it's a real bug/change in memory management, it'll get sorted out eventually -- till then I'm limited to running only 2 VMs. There's usually some pain associated with upgrading early, this appears to fall into that category...

Doug

--

dakeyras · ‎10-25-2013

It's definitely not just you. My case was similar - a 1GB ram vm (out of 4GB system) was basically unable to start, even after I closed essentially every other app.

There's a slightly longer thread on apple support communities where it seems that turning off app nap helped some people. It helped me, but I'm not sure why (maybe participating in app nap has implications about memory paging/compression on 10.9?).

dacmp · ‎10-25-2013

Thanks @dakeyras -- I hadn't seen that thread, I appreciate the reference. I've suspected something like the possible problem described there -- basically, that Fusion is bumping up against the new Mavricks' memory management magic -- but find it a bit implausible that the Fusion engineers wouldn't have seen/dealt with that before releasing 6.

Doug

--

e320_cdi · ‎10-25-2013

The issue that I am seeing is not nearly as severe as what others are by reading some of the posts. I have opened several VMs, to the point where I would expect an out of memory error, but I would think it would start paging out instead of give the out of memory error. I don't recall getting this in the past, however I am not sure if I have used it to this extent before.

dariusd · ‎10-25-2013

Hi folks,

Trying to collect a bit more information on this issue. If you are encountering the "Not enough physical memory is available..." error in Fusion after upgrading your host/s to Mavericks, please launch Terminal and run the command:

pmset -g

and paste that command's output into a reply in this thread. I'd also be interested to know the Model Identifier of the affected host/s (launch the System Information application, and look under Hardware).

Thanks!

--

Darius

dacmp · ‎10-26-2013

Thanks Darius, info below --

Doug

--

MacBookAir5,2

~ $ pmset -g

Active Profiles:

Battery Power -1*

AC Power -1

Currently in use:

standbydelay 4200

standby 1

halfdim 1

hibernatefile /var/vm/sleepimage

darkwakes 0

disksleep 10

sleep 5

autopoweroffdelay 14400

hibernatemode 3

autopoweroff 1

ttyskeepawake 1

displaysleep 3

acwake 0

lidwake 1

rav3n · ‎10-28-2013

hi Darius,

I have MacBookPro8,1 (early 2011 13") with 4Gb of RAM - I boot up a single Windows7 client in Fusion 6 and I get this error intermittently, sometimes I cannot start with even a single Mac application running, sometimes if I've started / shutdown the VM recently then the VM will start even with other apps running, I was running Fusion 6 on Lion and did not get this error, I have even reduced the VM memory allocation from 1512 to 1024 and this has made no difference.

pmset info below

Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

standbydelay 4200

standby 0

womp 1

halfdim 1

hibernatefile /var/vm/sleepimage

sms 1

networkoversleep 0

disksleep 0

sleep 0

hibernatemode 3

ttyskeepawake 1

displaysleep 10

acwake 0

lidwake 1

arang · ‎10-30-2013

Hi Darius,

I'm not sure why power management might come into play, but here you go:

Battery Power -1*

AC Power -1

Currently in use:

standbydelay 4200

standby 1

halfdim 1

hibernatefile /var/vm/sleepimage

darkwakes 1

disksleep 10

sleep 10

hibernatemode 3

ttyskeepawake 1

displaysleep 2

acwake 0

lidwake 1

Here's some information from the log files.

2013-10-23T17:26:43.859-06:00| vmx| I120: HV Settings: virtual exec = 'hardware'; virtual mmu = 'hardware'

2013-10-23T17:26:43.868-06:00| vmx| I120: OvhdMem_PowerOn: lib/overheadmem: paged 626512 nonpaged 37106 anonymous 18340

2013-10-23T17:26:43.868-06:00| vmx| I120: OvhdMem_PowerOn: initial admission: paged 590517 nonpaged 36271 anonymous 5715

2013-10-23T17:26:43.868-06:00| vmx| I120: VMMEM: Initial Reservation: 1270MB (MainMem=1200MB)

2013-10-23T17:26:43.868-06:00| vmx| I120: MemSched_PowerOn: balloon minGuestSize 104857 (80% of min required size 131072)

2013-10-23T17:26:43.868-06:00| vmx| I120: MemSched: reserved mem (in MB) min 128 max 2456 recommended 2456

2013-10-23T17:26:43.868-06:00| vmx| I120: PShare: enabled 1 adaptive 1 scanRate [16, 400]

2013-10-23T17:26:43.868-06:00| vmx| I120: MemSched: pg 590517 np 36271 anon 5715 mem 307200

2013-10-23T17:26:43.868-06:00| vmx| I120: MemSched: numvm 1 locked pages: num 0 max 152447

2013-10-23T17:26:43.868-06:00| vmx| I120: MemSched: locked Page Limit: host 160639 config 628736 dynam -1

2013-10-23T17:26:43.868-06:00| vmx| I120: MemSched: minmempct 50 minalloc 0 admitted 0

2013-10-23T17:26:43.868-06:00| vmx| I120: Msg_Post: Error

2013-10-23T17:26:43.868-06:00| vmx| I120: [msg.memsched.preNotEnoughMem] Not enough physical memory is available to power on this virtual machine with its configured settings.

2013-10-23T17:26:43.868-06:00| vmx| I120: [msg.memsched.hostUnderDuress] 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.

2013-10-23T17:26:43.869-06:00| vmx| I120: [msg.memsched.postNotEnoughMem] 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.

2013-10-23T17:26:43.869-06:00| vmx| I120: ----------------------------------------

2013-10-23T17:26:47.088-06:00| vmx| I120: Module MemSched power on failed.

I had three failures with the above, then a successful poweron:

2013-10-23T17:42:32.358-06:00| vmx| I120: MemSched_PowerOn: balloon minGuestSize 104857 (80% of min required size 131072)

2013-10-23T17:42:32.358-06:00| vmx| I120: MemSched: reserved mem (in MB) min 128 max 2456 recommended 2456

2013-10-23T17:42:32.358-06:00| vmx| I120: PShare: enabled 1 adaptive 1 scanRate [16, 400]

2013-10-23T17:42:32.358-06:00| vmx| I120: MemSched: pg 590517 np 36271 anon 5715 mem 307200

2013-10-23T17:42:32.358-06:00| vmx| I120: MemSched: numvm 1 locked pages: num 0 max 221682

2013-10-23T17:42:32.358-06:00| vmx| I120: MemSched: locked Page Limit: host 229874 config 628736 dynam -1

2013-10-23T17:42:32.358-06:00| vmx| I120: MemSched: minmempct 50 minalloc 0 admitted 1

2013-10-23T17:42:32.358-06:00| vmx| W110: NUMA: automatic VM sizing request ignored

The "locked pages" and "locked Page Limit" seem to be the most relevant, though it's not obvious to me whether VMware Fusion was deciding there wasn't enough memory based on what Mavericks was reporting to it, or whether it made an attempt to allocate/wire memory and Mavericks failed to fulfill it.

hwinkel · ‎11-01-2013

I have exactly the same issue, Win7 VM configured with 1GB is not starting anymore with Fusion 6 and Mavericks. MB Air 2011 4GB RAM.

hwinkel · ‎11-01-2013

One update to this topic. i'm running the latest Skype 6.9. After closing Skype I was able to start my VM. Closing other applications does not help me. May this could be related ?

dmsc · ‎11-01-2013

I've got the same issue here. After upgrading to 10.9 and VMWare 6 Pro, my virtual machines are working in the first few minutes after rebooting the computer, but only with reduced vm memory, then stop working by killing Windows (with all the negative effects, loss of data and registration). Trying to start VMWare later after rebooting I get a error message about missing physical memory.

Never had those problems with VMware up to version 5. This has to be fixed asap, as I need virtual machines for business. I'll try to go back to version 5, or will have to switch to another vendor if that does not work either. Did anyone ever test VMWare 6.0.1 with Mavericks? I doubt it.

dmsc

MacBookAir 4,1

Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

standbydelay 4200

standby 1

womp 1

halfdim 1

hibernatefile /var/vm/sleepimage

darkwakes 1

networkoversleep 0

disksleep 10

sleep 180

hibernatemode 3

ttyskeepawake 1

displaysleep 60

acwake 0

lidwake 1

rav3n · ‎11-03-2013

I don't run Skype... I have to shutdown almost all running applications, mail, safari...

If I have no apps running from the dock then I can start my vm every time, if I have just one app like safari open then it fails with a memory error but I have 4Gb ram + 5Gb swap and nothing running but mavericks - surely 10.9 cant be that greedy...

j0ni · ‎11-04-2013

Another data point:

MacBookAir4,1

Active Profiles:

Battery Power -1*

AC Power -1

Currently in use:

standbydelay 4200

standby 1

halfdim 1

hibernatefile /var/vm/sleepimage

darkwakes 0

disksleep 10

sleep 10

hibernatemode 3

ttyskeepawake 1

displaysleep 2

acwake 0

lidwake 1

herby1961 · ‎11-05-2013

it looks that 6.0.2 that was released today solved the problem:

Resolved an issue that causes virtual machines to fail to power on due to insufficient memory.

I will try it next weekend. maybe someone can share his experience with 6.0.2

regards

Herbert

dacmp · ‎11-05-2013

Thanks @herby1961 -- I've just tested 6.0.2, and confirm it resolves my original issue -- I can now load the same set of VMs I could load in V5, they remain responsive, seem stable.

Thanks @dariusd & VMWare team for the quick fix, it's very much appreciated.

Doug

--

herby1961 · ‎11-05-2013

Hi Doug,

as you reported that the update helped i installed it also and now i can start on a macbook air with 4 GB RAM 2 Guests with each 1 MB RAM (1 Windows 7, 1 Windows 😎 with out problems.

thanks also for the quick fix to the VMWare team.

dariusd · ‎11-05-2013

Thanks for your patience and for reporting back with your success, Doug and Herbert!

Just for the record, there were actually two separate issues addressed by the 6.0.2 update: One would affect users upgrading from Fusion 5 to Fusion 6 (regardless of the OS X version of the host machine) due to an error in the way we computed the memory which we needed to reserve for the host OS, and another would affect users running Fusion on Mavericks specifically, due to a problem brought about by the new Memory Compression technology in Mavericks. Both would lead to Fusion issuing the same "Not enough physical memory" error message.

Hopefully Fusion 6.0.2 will now save its complaints for when there is really insufficient memory.

If you do continue to encounter this problem with Fusion 6.0.2 (whether on Mavericks or not) when you believe you do have sufficient memory available, please do post back with the details!

Thanks,

--

Darius

rav3n · ‎11-06-2013

Thanks for the fix Vmware - my machine is back to normal service too

All

Upgraded to V6 now seeing: "Not enough physical memory is available to power on this virtual machine with its configured settings.". This did not occur in V5.