Opened 14 years ago
Closed 9 years ago
#8409 closed defect (obsolete)
Unable to allocate and lock memory
| Reported by: | Sylvain Ragab | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.4 |
| Keywords: | Memory | Cc: | |
| Guest type: | Windows | Host type: | Mac OS X |
Description
Memory used by a guest operating system (With Ubuntu & W7) reaches about 2’750GB (regardless of the amount of memory configured), the virtual machine will crash with a errorID=HostMemoryLow message="Unable to allocate and lock memory' error even if there is free memory available on the host.
Attachments (3)
Change History (8)
by , 14 years ago
| Attachment: | W7_Perso-2011-02-23-08-49-11.log added |
|---|
comment:1 by , 14 years ago
by , 14 years ago
| Attachment: | W7_Perso-2011-02-23-10-38-08-worked.log added |
|---|
comment:3 by , 14 years ago
You are running the 32bit version of VirtualBox. To use more memory you need to boot your Mac OS X into the real 64-bit mode. This explains how to do this.
comment:4 by , 14 years ago
I am seeing similar problem on Solaris 11 Express, virtualbox 4.0.4 attempting to boot an AI client install ISO.
No other VBox clients running, Base Memory set to 1024MB, there is 8GB (8191MB) of RAM on host OS, and 4GB of swap in rpool/swap.
There's virtually nothing else running on this machine, so why would I be getting this error ? Attached VBox.log for reference, tried setting Base Memory on client ro 2048, 1024, 900, 800.
900 and 800 settings did get a little further but bombed with same error before boot completed.
comment:5 by , 9 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
The log shows that the VM was configured to use about 2,8GB of RAM:
So the memory used by VM process can reach 2,7GB, which is probably a limit on the 32 bit host OS, which you use.
You said: "Memory used by a guest operating system (With Ubuntu & W7) reaches about 2’750GB (regardless of the amount of memory configured)". How much guest RAM have you tried to configure? Could you please attach a VBox.log with the same problem for a VM with for example 1,5GB guest RAM?