Failed to allocate specified amount of memory

Jul 8, 2007, 08:38 PM #1
wellesgoodrich@mac.com Junior Member Join: Jan 2007 Posts: 11	Failed to allocate specified amount of memory (I posted this message in the wrong forum already so I'm reposting it here as it is a Mac question.) When I try to launch Windows XP Pro via Parallels Desktop 3.0 (build 4128) on a Mac Pro 266, 4GB RAM, 4 internal HDs, NVIDIA GeForce 7300 GT I get the following error message... "Parallels Desktop failed to allocate the specified amount of memory. Please restart Parallels Desktop and try again. To avoid this problem in the future choose from the menu: Parallels Desktop > Preferences. On the Memory tab select the "Enable virtual memory preallocation" option." This error just started for no apparent reason. If I restart my computer Windows launches and runs just fine (except for the failure when dragging single files from Windows to the Mac desktop.) I believe it is the case that this failure to launch occurs after my computer is put in sleep mode and then 'awaken.' Has anyone else seen this issue? Should my next troubleshooting step be a reinstall of Parallels? Thanks for any advice.
Reply

Jul 8, 2007, 08:38 PM

wellesgoodrich@mac.com
Junior Member

Join: Jan 2007
Posts: 11

Failed to allocate specified amount of memory

(I posted this message in the wrong forum already so I'm reposting it here as it is a Mac question.)

When I try to launch Windows XP Pro via Parallels Desktop 3.0 (build 4128) on a Mac Pro 266, 4GB RAM, 4 internal HDs, NVIDIA GeForce 7300 GT I get the following error message...

"Parallels Desktop failed to allocate the specified amount of memory.
Please restart Parallels Desktop and try again.
To avoid this problem in the future choose from the menu: Parallels Desktop > Preferences. On the Memory tab select the "Enable virtual memory preallocation" option."

This error just started for no apparent reason. If I restart my computer Windows launches and runs just fine (except for the failure when dragging single files from Windows to the Mac desktop.) I believe it is the case that this failure to launch occurs after my computer is put in sleep mode and then 'awaken.'

Has anyone else seen this issue? Should my next troubleshooting step be a reinstall of Parallels? Thanks for any advice.

Jul 9, 2007, 04:30 AM #2
Ankou Guest Join: Posts: n/a	Hello wellesgoodrich What amount of RAM are you trying to allocate to your VM?
Reply

Jul 9, 2007, 08:36 AM #3
wellesgoodrich@mac.com Junior Member Join: Jan 2007 Posts: 11	Hi Ankou, I have the Main memory allocation set to 1500MB, the maximum recommended in the Configuration Editor. In the preferences memory window, Adjust memory limit Automatically is selected and Enable virtual memory preallocation is checked.
Reply

Jul 9, 2007, 08:43 AM #4
Ankou Guest Join: Posts: n/a	Thank you for for the information. We are aware of this problem in current version of Parallels Desktop and there is update coming soon that should solve this issue.
Reply

Jul 9, 2007, 10:04 AM #5
wellesgoodrich@mac.com Junior Member Join: Jan 2007 Posts: 11	Thank you for the information. I'm rather relieved that it isn't just my computer.
Reply

Jul 12, 2007, 09:06 PM #6
jwendolo Junior Member Join: Jul 2007 Posts: 4	Memory error may be disk I was getting this error too. In my case the disk partition where the VM file was stored was almost out of space. I freed up some space and the problem was solved
Reply

Jul 16, 2007, 05:00 AM #7
drewfreyman Junior Member Join: Jul 2007 Posts: 3	Solving Sudden Occurrence of Failure to Allocate Memory Problem After a lot of grief I think I have the solution to this problem. At least this method worked for me: 1. Reinstall OS X from the original install disks being sure to choose the "archive" type of reinstallation. 2. Reboot. 3. Try Parallels. If the error message comes up again, try uninstalling Parallels, restarting OS X, and reinstalling Parallels. Reboot. At least in my case, the root cause of the problem seemed to be a software update from Apple to OS X on 7/4/07. So, I needed to roll back the updates. I called Apple and the phone rep described the method above.
Reply

Jul 16, 2007, 05:00 AM

drewfreyman
Junior Member

Join: Jul 2007
Posts: 3

Solving Sudden Occurrence of Failure to Allocate Memory Problem

After a lot of grief I think I have the solution to this problem. At least this method worked for me:
1. Reinstall OS X from the original install disks being sure to choose the "archive" type of reinstallation.
2. Reboot.
3. Try Parallels. If the error message comes up again, try uninstalling Parallels, restarting OS X, and reinstalling Parallels. Reboot.

At least in my case, the root cause of the problem seemed to be a software update from Apple to OS X on 7/4/07. So, I needed to roll back the updates. I called Apple and the phone rep described the method above.

Jul 16, 2007, 05:16 PM #8
wellesgoodrich@mac.com Junior Member Join: Jan 2007 Posts: 11	Thanks for that tip, drewfreyman. My Parallels 3.0 won't even let me launch Windows at all any more. Unfortuately, an archive and install just isn't a desirable solution for me as I have such a complicated system with some 200 licensed applications and everything is working on OS 10.4.10 except Parallels. I'll wait for a new build to be released, I guess. In the meantime, I'm giving Fusion a try. It works well but I do prefer Coherence over Unity.
Reply

Jul 16, 2007, 05:16 PM

wellesgoodrich@mac.com
Junior Member

Join: Jan 2007
Posts: 11

Thanks for that tip, drewfreyman. My Parallels 3.0 won't even let me launch Windows at all any more. Unfortuately, an archive and install just isn't a desirable solution for me as I have such a complicated system with some 200 licensed applications and everything is working on OS 10.4.10 except Parallels. I'll wait for a new build to be released, I guess. In the meantime, I'm giving Fusion a try. It works well but I do prefer Coherence over Unity.

Jul 16, 2007, 08:10 PM #9
drewfreyman Junior Member Join: Jul 2007 Posts: 3	Ability to Preserve State of OS X on Re-install Believe it or not, this method of re-installation PRESERVED all my apps, settings, etc. from the current OS X. Even my wallpaper. The only thing that it didn't seem to preserve was the password to my home wLAN. Also, it preserves the "previous" OS X configuration, completely, in a new multi folder (its big--like 20GB) on your drive. I believe there is a method to re-instate from this folder if you don't like the re-install. It could be risk free for you to try. This might work out for you after all...
Reply

Jul 16, 2007, 08:10 PM

drewfreyman
Junior Member

Join: Jul 2007
Posts: 3

Ability to Preserve State of OS X on Re-install

Believe it or not, this method of re-installation PRESERVED all my apps, settings, etc. from the current OS X. Even my wallpaper. The only thing that it didn't seem to preserve was the password to my home wLAN. Also, it preserves the "previous" OS X configuration, completely, in a new multi folder (its big--like 20GB) on your drive. I believe there is a method to re-instate from this folder if you don't like the re-install. It could be risk free for you to try. This might work out for you after all...

Jul 18, 2007, 01:00 PM #10
tshealy Junior Member Join: Jul 2007 Posts: 1	ETA for Fix? I am experiencing the same problem. Can anyone provide an explanation of why the issue occurs? Also, would it be possible to get a rough ETA for the fix (beta or production-ready). Thanks. -Tom
Reply

Jul 20, 2007, 11:47 AM #11
kel Junior Member Join: Jul 2007 Posts: 2	i configured 1024mb for windows xp, it seemed to work with the following "workaround" i m using build 4560. i had that memory allocation error when trying to set 1024gb memory for my windows xp home. here is what i did to make that mem err goes away. my macbook pro has 4gb of mem. 1) close all apps, esp. those that take lot of memory, eg. firefox. 2) install iFreeMem from apple download site, this is a shareware?? but there is a trial period you can test it out. 3) Run iFreeMem, and hit that "Optimize Memory" button. 4) BEFORE starting any other, launch your parallel desktop, and run the VM. this works for me. i dont know enuf technical details but I suspect this may be related to memory management. that tool kind of freed up the Inactive memory and made it available for Parallel. so launching it first before others help. Pls send a reply if this works for you, I want to know if this even depends on the type of Host OS ?? 'cos I plan to install different favor of linux on it. Regards, -kel
Reply

Jul 20, 2007, 11:47 AM

#11

kel
Junior Member

Join: Jul 2007
Posts: 2

i configured 1024mb for windows xp, it seemed to work with the following "workaround"

i m using build 4560. i had that memory allocation error when trying to set 1024gb memory
for my windows xp home. here is what i did to make that mem err goes away. my macbook pro has 4gb of mem.

1) close all apps, esp. those that take lot of memory, eg. firefox.
2) install iFreeMem from apple download site, this is a shareware??
but there is a trial period you can test it out.
3) Run iFreeMem, and hit that "Optimize Memory" button.
4) BEFORE starting any other, launch your parallel desktop, and run
the VM.

this works for me. i dont know enuf technical details but I suspect this may
be related to memory management. that tool kind of freed up the Inactive
memory and made it available for Parallel. so launching it first before
others help.

Pls send a reply if this works for you, I want to know if this even depends on
the type of Host OS ?? 'cos I plan to install different favor of linux on it.

Regards,

-kel

Jul 21, 2007, 08:46 AM #12
wellesgoodrich@mac.com Junior Member Join: Jan 2007 Posts: 11	Kel, I was impressed enough by your logic and solution to try it out myself. However, first I should add that I've added 8GB more RAM to my system so I'm now running with 12GB total. I did download and install iFreeMem. After running it I had more than 11GB RAM free. I also eliminated all traces of any old Parallels installations (including the VMs) via the uninstaller followed up by a search for any Parallels related files. I performed a new install of Parallels 4560 and Windows XP SP2. That went OK. However the first time I tried to start Windows from the Parallels desktop window I got the old memory allocation warning and no launch. I was able to use the Windows XP.pvs file as a launcher successfully for about a half a dozen launches and then the dreaded memory allocation warning reared it's ugly head and Parallels became totally useless. Thanks for the suggestion. It seemed like a good idea.
Reply

Jul 21, 2007, 08:46 AM

#12

wellesgoodrich@mac.com
Junior Member

Join: Jan 2007
Posts: 11

Kel,

I was impressed enough by your logic and solution to try it out myself. However, first I should add that I've added 8GB more RAM to my system so I'm now running with 12GB total.

I did download and install iFreeMem. After running it I had more than 11GB RAM free. I also eliminated all traces of any old Parallels installations (including the VMs) via the uninstaller followed up by a search for any Parallels related files. I performed a new install of Parallels 4560 and Windows XP SP2. That went OK. However the first time I tried to start Windows from the Parallels desktop window I got the old memory allocation warning and no launch. I was able to use the Windows XP.pvs file as a launcher successfully for about a half a dozen launches and then the dreaded memory allocation warning reared it's ugly head and Parallels became totally useless.

Thanks for the suggestion. It seemed like a good idea.

Jul 22, 2007, 07:54 PM #13
wellesgoodrich@mac.com Junior Member Join: Jan 2007 Posts: 11	This is my last post. I tried one more time to get Parallels 3.0 to work by doing a completely new installation of the latest build 4560. The first launch, to install Windows XP resulted in the dreaded 'Failed to allocate specified amount of memory' warning. I quit and will try to get my upgrade payment refunded as I've never gotten 3.0 to work, there has been no response or solution provided, the problem hasn't been addressed in three public releases of 3.0, and I've wasted a huge amount of time. VMware Fusion works. Bye.
Reply

Jul 22, 2007, 07:54 PM

#13

wellesgoodrich@mac.com
Junior Member

Join: Jan 2007
Posts: 11

This is my last post. I tried one more time to get Parallels 3.0 to work by doing a completely new installation of the latest build 4560. The first launch, to install Windows XP resulted in the dreaded 'Failed to allocate specified amount of memory' warning. I quit and will try to get my upgrade payment refunded as I've never gotten 3.0 to work, there has been no response or solution provided, the problem hasn't been addressed in three public releases of 3.0, and I've wasted a huge amount of time. VMware Fusion works.

Bye.

Jul 24, 2007, 01:14 PM #14
rjonna Junior Member Join: Jul 2007 Posts: 1	a fix that seems to work, though this issue still needs resolved I simply lowered the VM memory to around 684 and the machine powered up fine. I will report back with any further failure. I then installed parallel tools (again) as this popped up (after the 4560 update). I shut down and got an error, as before, when i tried to ramp up the VM memory any higher than 684. So, I changed the program memory (in Parallels preferences) to as high as it could go (around 2.5gb on my macbook pro) and the error i was getting in my VM memory disappeared. I set the VM memory at 1gb and it seems to work fine. I will report back with any further failure.
Reply

Jul 24, 2007, 01:14 PM

#14

rjonna
Junior Member

Join: Jul 2007
Posts: 1

a fix that seems to work, though this issue still needs resolved

I simply lowered the VM memory to around 684 and the machine powered up fine. I will report back with any further failure.

I then installed parallel tools (again) as this popped up (after the 4560 update). I shut down and got an error, as before, when i tried to ramp up the VM memory any higher than 684. So, I changed the program memory (in Parallels preferences) to as high as it could go (around 2.5gb on my macbook pro) and the error i was getting in my VM memory disappeared. I set the VM memory at 1gb and it seems to work fine. I will report back with any further failure.

Jul 31, 2007, 07:08 PM #15
kel Junior Member Join: Jul 2007 Posts: 2	In my preferences, i checked the "Enable virtual memory preallocation" option, i left the "Adjust memory limit" as Automatically.
Reply

Aug 24, 2007, 12:06 AM #16
Ribozyme Junior Member Join: Jul 2007 Posts: 4	Well, I have now installed VMware and not only is much faster, but I am able to allocate up to 8 GB RAM and two virtual procesors. The interface is a little klunky as compares to Parelles, but it works!
Reply

Aug 24, 2007, 05:39 PM #17
hEADcRASH Junior Member Join: Jul 2007 Posts: 5	Here's a bump RealityExplorer :-) ...I have also recently installed VMWare... And while the multiprocessor support and >8G memory features are nice... ...it WORKS. I'm keeping my word about trying the next Parallels patch, but at least I won't be without a safety net! ::Glenn
Reply

Aug 24, 2007, 06:01 PM #18
brkirch Senior Member Join: Dec 2006 Posts: 422	The latest beta has some improvements in memory management. 2 GB of memory per VM is now supported and a total of more than 4 GB for multiple VMs is supposed to be supported.
Reply

Aug 24, 2007, 08:36 PM

#19

hEADcRASH
Junior Member

Join: Jul 2007
Posts: 5

Nope -- that's it -- game over...

The latest version (I do not care if it is being labeled "beta") still does not work. Same error. Same suggestion to "reboot the machine and try again." That is just not going to happen every time I want to use Parallels.

I will post again if I have a negative experience obtaining a refund.

::Glenn

Attached Images

fail.png (16.9 KB, 13 views)

Sep 8, 2007, 01:54 PM

#20

Relan
Parallels Team

Join: May 2007
Posts: 125

Quote:

Originally Posted by hEADcRASH

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.

Post Reply

« Previous Thread | Next Thread »

1 | 2 | >

Search this thread	Forum jump
Advanced Search

Thread tools	Display modes
Printable Version Email this Page	Linear Mode Hybrid Mode Threaded Mode

Parallels Technology Network

Failed to allocate specified amount of memory