Unable to allocate memory for VMM purposes.

Discussion in 'Installation and Configuration of Parallels Desktop' started by WilliamU, Aug 13, 2015.

  1. WilliamU

    WilliamU Junior Member

    Messages:
    15
    Hi, I only installed this software yesterday and I am using the 14 day trial (but I have ordered a license via the Apple store).

    This message (see subject and image) appears when I click on the 'Power button' of my only VM on the Parallels Desktop, so why it is producing this error I do not know. If I close this dialog then click the 'Click to start' link the machine starts up as expected! So as all this is very new to me I thought I'd post this here as something is not right and maybe someone can shed some light on this for me.

    My Mac spec is:
    iMac Retina 5K
    4HGz i7
    32GB 1600 MHz DDR3
    Running OS X Yosemite 10.10.4
     

    Attached Files:

  2. PaulChristopher@Parallels

    PaulChristopher@Parallels Product Expert Staff Member

    Messages:
    3,113
    Hi WilliamU,
    Please follow the steps suggested at http://kb.parallels.com/119927 to troubleshoot and resolve the issue.
     
    Last edited by a moderator: Aug 13, 2015
  3. WilliamU

    WilliamU Junior Member

    Messages:
    15
    Thanks for the quick response, appreciated. I have implemented your suggestion and it has fixed the aforementioned, but can you tell me what that flag setting does please?
     
  4. PaulChristopher@Parallels

    PaulChristopher@Parallels Product Expert Staff Member

    Messages:
    3,113
    Hi WilliamU,
    Glad your issue has been resolved. If you resume Virtual Machine immediately after suspend then system call vm_protect that we use when VM is started which can fail in case of host and VM workload. So, this bootflag fixes this issue. Thanks!
     
  5. WilliamU

    WilliamU Junior Member

    Messages:
    15
    Well actually no, I didn't resume after a suspend. I was getting this error after a cold start of the Mac itself. Considering the machine was also idle at the time and with 32GB of memory how can this be related to workload, as it had none; with the exception of bootstrapping the VM.
     
  6. WilliamU

    WilliamU Junior Member

    Messages:
    15
    Having upgraded to Parallels 11 when I started my Windows 8.1 VM this morning I got this very same error even though my boot flags still contain the vm.mem_anonymous=1.

    Any thoughts on this?

    P.S. I am now using my purchased license.
     
  7. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,121
    Hi, please sorry for the inconvenience, but how may Ram did you add to your VM?
     
  8. WilliamU

    WilliamU Junior Member

    Messages:
    15
    26232MB which is under the recommended range of 27764MB.
     
  9. WilliamU

    WilliamU Junior Member

    Messages:
    15
    Helllo, is there a fix for this as my Windows VM is refusing to start!

    I have an Arch Linux VM with 16Gb configured and it starts without issue.
     
  10. WilliamU

    WilliamU Junior Member

    Messages:
    15
    I (appear) to have fixed this now, by removing the boot flag as noted above, but I suspect this will be back the next time I reboot or restart Parallels.
     
  11. WilliamU

    WilliamU Junior Member

    Messages:
    15
    Me again. Having turned on my Mac this morning I started Parallels 11, clicked the 'Power On' button and the VM started without issue! Can someone from Parallels please comment on this. I am assuming that the issue in version 10 where the boot flag was required has since been resolved in v11, is this correct?
     
  12. WilliamU

    WilliamU Junior Member

    Messages:
    15
    My Windows VM has worked every day since my last post. However, this morning I am now getting this error again, having made no changes to the VM. I tried adding the flag I removed previously to no avail. I've even tried restarting the machine out of desperation, but I simply can't start my MV. To say this is tedious would be an understatement. Does anyone know what is actually going on here, as it would appear that Parallels themselves either don't or are choosing to ignore this post.

    Prior to posting this I thought I would try something and I set my MV's memory to be 16G and this time it started!
     

Share This Page