Parallels Desktop failed to allocate the specified amount of memory

B

bmwmcrider

Member
I just installed a larger HD in my MacBook Pro and fully restored the all the files from the old drive to the new one using SuperDuper. I launched Parallels and attempted to start my WinXP VM when the above message appeared. One of the items in the message was a suggestion to enable the virtual memory preallocation unde the memory tab which was already done.

So my question is why is this message appearing and what can I do to resolve the situation? I do not want to have to reinstall the WinXP guest OS and all my Windows apps although I have an image of everything that was created using Acronis TrueImage.

Thanks,

Mike
 
I followed the instructions in the reference you cited. Now when I launch Parallels a dialog pops up stating "The application Parallels Desktop quit unexpectedly". So what is the cause of this problem and how is it corrected?

Thanks for your interest in my problem,

Mike
 
same original issue

I am seeing the exact same issue "Parallels Desktop failed to allocate the specified amount of memory" after
upgrading my HD and using SuperDuper to copy everything over.

I uninstalled parallels desktop and reinstalled.
I am running Mac OSX 10.5.5 and Parallels 3.0 build 5626

I find if I lower the memory to 1024MB, the old VMs (Linux and windows) work. but even creating new VMs
with greater than 1024MB fail. I need the larger memory for what I use this for.

any additional info on this? anyone tried this with Parallels 4.0?
are there any logs or any way to find out what Parallels is failing when this is happening?
the error displayed is misleading as my "Enable virtual memory preallocation" is checked.
 
Me Too

I have also having the same symptoms very frustrating.

I can no longer assign more than 1G to my VM. I too got a new harddrive and ported over.

I followed the instructions of repairing permissions and reinstalling to no avail.

I am using Parallels Desktop 3.0 Build 5584, OSX 10.5.5

Please Help
 
Please go to Parallels Desktop => Preferences, open the Memory tab and make sure that a) enable memory preallocation checkbox is checked and b)you are not trying to give your Virtual Machine more memory than you have allocated. Try playing with the manual/automated settings and see if the situation improves. Be advised that in some *very* rare cases 'enable memory preallocation' flag got messed up, so that checking the checkbox actually disabled the feature and vice versa. See if this is not the case here.

Another possible way to rectify this is to launch Parallels Desktop first thing after your Mac boots. This is effective in some cases.

Also jtushman, on a bit of an unrelated note you may wish to update to the latest build of Parallels Desktop 3. Get your red hot latest build here!

http://www.parallels.com/download/file/v3/en/GA/Parallels-Desktop-5626-Mac-en.dmg
 
Thank you for your quick response.

I tried all that you have suggested, including installing the latest version. Sorry to say, I had no luck. I am trying allocate 2GB. When I launch the VM *right* after I boot up I have 3.13GB free (out of 4 total) I also Have 32GB of HD space.

Do you have any other ideas? I would love to get this working.

Thank you,

Jonathan
 
We are starting to see this problem also. Updating to the latest build did not fix the issue and reinstalling OS X seems a bit extreme. Any other thoughts?
 
Not necessary to reinstall Mac OS
Try following:
1. reinstall 10.5.5 update
2. Repair permissions
3. Navigate to VM folder and delete .mem and .sav files
4. try to assign 1,5 GB of memory
 
Add one more user with identical problem

Can you advise where I can find .sav and .mem files. I looked under library/parallels/winxp.1 and found no such files. Also will an upgrade to 4.0 fix this issue. I have already purchased 4.0 but have not installed. I have been reluctant to upgrade until this issue is resolved in 3.0

Thanks
Jeff
 
Success

I follow the instructions above except that I did not delete .sav or .mem files (couldn't find any) and it worked. I had previously already run Cocktail which fixed permissions but that did not fix the issue. I reloaded 10.5.5, fixed permissions again, this time with disk utility and the virtual machine launched okay this time. Odd.

Thanks for the help.
 
Just FYI - .sav and .mem are swap files generated by a running or suspended Virtual Machine and are deleted automatically when VM shuts down. If you cannot find them - that means your Virtual Machine has been shut down properly.
 
3. Navigate to VM folder and delete .mem and .sav files

This step seemed to fix it for me. Thanks!!
 
You must log in or register to reply here.
Back
Top