PAE Mode and memory error...

P

penrod

Junior Member
Ok, help me out. What "boot loader" are they talking about here? The guest os is Suse 10

===cut===
Parallels Workstation experience problem when trying to allocate physical memory in PAE mode. The current version of Parallels Workstation supports up to 4 GB of physical memory. To fix the problem you have to change the auto detected memory size to 4096MB. Add to your boot loader the following option "mem=4096M".
===cut===
 
Hi,

Seems like a bug. We'll address this one.
Meanwhile, please just try to decrease the guest RAM amount assigned to the VM. What's its current number?
 
RAM is set to 256Mb. About as low as I can go with it. :)

Thanks for the reply.

John P.

PS: Great app so far though!
 
And what's the host's total physical memory available?

One more suggestion - downgrade the "Memory available for all VMs" in Parallels Workstaion->Preferences->Memory to something like 400 MB.
 
Hey Tim,

Total memory is 1Gb.

Just as an fyi... I just saw the same error with the quest OS being solaris 10.

In both cases, clicking ok and clicking on start a couple times makes it start working.

John P.
 
Memory error

I got this same memory error after I increased the memory for a VM that was already created. The VM was created with 256MB (the default). Later I changed the memory for the VM to 384MB and when I started the VM I got the same error message. I changed the memory for that VM back to 256MB and it works again. Weird. This is on a MBP 2.0GHz with 1GB DRAM.

When I create a new VM at 384MB it works fine ... although you have to reinstall everything.
 
I'm getting the same error with a Mac Pro with 4GB of RAM. And clicking "OK" doesn't make it go away and resetting to the original Memory setting doesn't make it go away. Essentially just broken. :(
 
Help! memory message

"Unable to allocate VM memory" – I've ininstalled and reinstalled Parallels twice, deleted preferences, expanded the memory using the HD utility. I can't think what else to do. I've got two VMs trapped inside my Mac, which have been working perfectly happily and now they're both locked inside a disk image that can't be accessed. Anyone else had this trouble?
Advice of whatever kind gratefully received.

Stephen
 
You must log in or register to reply here.
Back
Top