Parallels Forums
> Desktop Virtualization Products Discussion > Parallels Desktop for Mac > Windows Guest OS Discussion  
Failed to allocate specified amount of memory  
  

Failed to allocate specified amount of memory

Aug 25, 2007, 01:07 AM
#1  

Mike Boreham
Senior Member


Join: Dec 2006
Posts: 104
After updating to 5120 I put the memory to 1700 on my MacPro and straight away got "the unable to allocate" message. BUT I restarted as suggested and it has been OK for several starts since then.
Reply 
Aug 27, 2007, 04:28 PM
#2  

hEADcRASH
Junior Member


Join: Jul 2007
Posts: 5
<insert sound of toilet flushing here>
Hello Glenn,

Thank you for your email. Parallels offers an 30 day money back. Refunding
the product depends on how your originally purchased it. Where and how did
you purchase the product?

For the record: I purchased the original (crippled: can you say intermittent kernel panics on a Quad Pro?) version last year (along with 3 other copies for friends). From here on out my recommendations will only be VMware.

Version 5060 is a Beta version if this is the version that you are using.

Parallels is under no obligation to provide technical support under the
terms of this license, and provides no assurance that any specific errors or
discrepancies in the Software will be corrected.
(emphasis mine)

We appreciate your email and thank you for supporting Parallels.

Obviously I wish they had read my email and the link to the thread I included.

Have a great day!

WTF?


Customer Support Services
Parallels, Inc
www.parallels.com
Reply 
Aug 30, 2007, 12:32 AM
#3  

chrishch
Junior Member


Join: Mar 2007
Posts: 6
I bought two pieces of 1GB Mushkin Memory for my MacBook (Core2 2.0GHz) and they were defective. I had been running my Parallels Windows XP VM at 1024MB before, and it was fine, but constantly getting BSODs. After sending the memory back, I adjusted my VM to use 512MB.

Then, today, I finally got my replacement memory, and cranked up the Memory back to 1024MB. I had always used 1024MB before, but now, I get the "failed to allocate" error. Nothing has changed, as I have always had Parallels 3 build 4128.

I did a search and found this thread. I then tried changing the memory size of my VM from 864 all the way up to 1004 and it won't allow for anything more 1004MB, and my video memory is set at only 4MB.

I'm not sure if upgrading to build 4560 will help, as I had other problems with it before, probably due to bad memory, but since reading this thread, it looks like it won't be fixed until the next build (or beyond). Can anyone help? Thanks.
Reply 
Sep 8, 2007, 02:00 PM
#4  
Relan's Avatar

Relan
Parallels Team


Join: May 2007
Posts: 125
Quote:
Originally Posted by chrishch
I'm not sure if upgrading to build 4560 will help, as I had other problems with it before, probably due to bad memory, but since reading this thread, it looks like it won't be fixed until the next build (or beyond). Can anyone help? Thanks.
Build 4560 will not fix "failed to allocate memory" error, but latest RC will.
Reply 
Sep 8, 2007, 04:11 PM
#5  

Eru Ithildur
Senior Member


Join: Jan 2007
Posts: 2,046
The key with rebooting is to do it DIRECTLY after the install, not after you try and it fails.
Try un-installing.
Reboot.
Install.
Reboot.
Now try to get in.
Reply 
Sep 9, 2007, 01:17 PM
#6  

stevegr1102
Junior Member


Join: Jun 2007
Posts: 2
Same problem here - frustrating - and I have a wrinkles.

Running Build 4560 (just checked for updates - Parallels says I am up to date). Brand new MacBook Pro 15" 2 GB RAM. Windows XP Home. 2 users on the computer with separate logins (in Mac-Land and in PC Land). Initially installed Parallels under one user (me). Fixed that (well, sort of - it feels like a hack, but was working - I'll do a separate post on that one).

When I try to boot Parallels from MY Mac login, I get the error described. It just started happening. Only think that changed was a Mac update of iTunes and one other thing - automatic stuff. I have tried the suggested fix re: automatically allocating memory - nada. HOWEVER - when I log into the Mac as my wife, Parallels lanuches (so far) with no trouble.

I am not sure whether we are actually launching the same VM or not - I am thinking we are NOT, though I think we ARE using the same Windows partition. This was a PARALLELS install - I am not using a Bootcamp partition or XP installation. Anyway - I sense that the error message is telling me something about Parallels, not XP...it does not seem to get that far.

Parallels team - this appears to have been going on for several months from the thread. By when - what promises ARE you willing to make regarding a fix. If none - I should probably go to VMWare as I depend on being able to run Windows from time to time on this machine. The software is unusable as delivered as it will not even load. This is NOT a minor issue. This is a show stopper. Please be specific regarding what promises you can make. To do less is to hide behind the technical terms of your license, but does no pass the test of reasonableness (especially given that this has been going on for some time). Thank you
Reply 
Sep 9, 2007, 01:59 PM
#7  

brkirch
Senior Member


Join: Dec 2006
Posts: 422
Quote:
Originally Posted by stevegr1102
Parallels team - this appears to have been going on for several months from the thread. By when - what promises ARE you willing to make regarding a fix. If none - I should probably go to VMWare as I depend on being able to run Windows from time to time on this machine. The software is unusable as delivered as it will not even load. This is NOT a minor issue. This is a show stopper. Please be specific regarding what promises you can make. To do less is to hide behind the technical terms of your license, but does no pass the test of reasonableness (especially given that this has been going on for some time). Thank you
The next update should not have this problem. In the meantime you can use the release candidate version of the update (make sure that you restart your computer after installing it).
Reply 
Sep 10, 2007, 02:34 AM
#8  
Relan's Avatar

Relan
Parallels Team


Join: May 2007
Posts: 125
Quote:
Originally Posted by stevegr1102
By when - what promises ARE you willing to make regarding a fix.
The bug is already fixed in current RC. Release will be out this week.
Reply 
Sep 12, 2007, 08:29 PM
#9  

skeedatl
Junior Member


Join: Sep 2007
Posts: 26
Quote:
Originally Posted by Relan
If you followed the advice and rebooted you Mac after new beta build installation you would find allocation bug fixed...

After you install Parallels on a Mac with more than 4 GB of memory it's highly recommended to reboot Mac if Parallels asks to do so....
...The bug is already fixed in current RC. Release will be out this week.
It's not fixed for me. When "this week". I just DLed the latest build of 5160 on 9/12/07 and I still have failed to allocate errors despite trying many VM memory combinations as well as rebooting the Macs many times.

http://forum.parallels.com/showthread.php?t=16225
Reply 
Sep 18, 2007, 06:35 PM
#10  

zero
Junior Member


Join: Sep 2007
Posts: 2
Useless
I'm just a few days into my trial, and getting the "failed to allocate" error.

I tried all the memory preferences.

I tried uninstalling, reboot, reinstall, reboot.

My VM is a useless blot on my HD.

If this isn't fixed SOON, I'll go with VMWare Fusion. At least it WORKS.

MacBook 10.4.9
Reply 
Sep 18, 2007, 07:27 PM
#11  

skeedatl
Junior Member


Join: Sep 2007
Posts: 26
I'm in the same boat as you. 5160 breaks stuff and I can't wait around for support to try and figure out why 4560 works (in my case with multiple display adapters) and 5160 doesn't.
Reply 
Sep 18, 2007, 07:39 PM
#12  

BenInBlack
Senior Member


Join: May 2006
Posts: 374
i should have stayed at 4560, but never had issues till now, not the same as these, but crashing and lockups since 5160. What I am stuck with is question because of never having to do this before.

How do i downgrade? to 4560
Reply 
Sep 18, 2007, 09:54 PM
#13  

skeedatl
Junior Member


Join: Sep 2007
Posts: 26
Uninstall your current parallels install and then install the older version you want. Then go into your VM and uninstall Parallels Tools, reboot the VM then reinstall Parallels Tools (for the version you're running).
Reply 
Sep 19, 2007, 01:25 AM
#14  

BenInBlack
Senior Member


Join: May 2006
Posts: 374
Well the nice thing is the key was remembered when i uninstalled 5160 and installed build 4560. I had a backup of the VM prior to update so i just uninstalled, brought in backup, reinstalled and walla, back to stable build 4560.

thx
Reply 
Jul 1, 2009, 11:43 PM
#15  

RonnieR
Junior Member


Join: Jul 2009
Posts: 1
This problem had me scared there for a minute!
Ok, I figured out the problem. Well...for me anyway. I got the same error when I booted my Parallels "parallesls desktop failed to allocate the specidied amount of memory."

SOLUTION: Your low on hard drive space on the Host machine. It's that simple. You don't have to change the Parallels Desktop >>> Preferences >>> Memory >>> Enable Virtual Memory Allocation, check box. Well at least I didn't. Just free up some space, you pack rat! J/K :)

Hope this helps!!!
Reply 


< 12

Thread tools Display modes
Hybrid Mode