Opened 14 years ago
Closed 8 years ago
#7832 closed defect (obsolete)
Unable to allocate and lock memory
| Reported by: | Neil | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 3.2.12 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description (last modified by )
VBox version is 3.2.12.
Host OS - Windows 2003 E x64 12GB host memory, 1.1GB used by host
client OS - debian 5.0.5, allocated 512MB, up and running
client OS - winxp-64, allocated 4GB, error - Unable to allocate and lock memory, reduce it to 3GB and same error, reduce it to 2GB and it boots and runs. All vbox directories are excluded from any virus scan. Had been running until Windows host was rebooted.
client OS - Oracle EntLnx 5/64, allocated 4GB, up and running.
Have rolled back to 3.2.10 and still same issue. Currently 8GB memory is available on the Windows host.
Attachments (2)
Change History (10)
comment:1 by , 14 years ago
| Cc: | removed |
|---|
comment:2 by , 14 years ago
See attached log files.
Upon review, please provide further instructions on additional information / data required.
Cheers, N
comment:3 by , 14 years ago
Well, you've got less than 4 GB free when you start the VM that needs 4 GB. I don't know why you think 8 GB is available.
comment:4 by , 14 years ago
Out of the 4 logs one shows the failure you mentioned. The other VM sessions were indeed started with plenty of host memory free, but of course didn't fail either.
comment:5 by , 14 years ago
Ok, so here is another attachment with two log files and screencam.
- Start up of Windows XP-64 with 2048MB of memory allocated - successful
- Start up of Windows XP-64 with 4096MB of memory allocated - unsuccessful
I may be REALLY stupid and overlooking something, so those with greater wisdom than I can point out the error or what I have overlooked, I would greatly appreciate.
comment:6 by , 14 years ago
comment:7 by , 14 years ago
So, based on responses, and ongoing testing, a Windows 2003-64 does not support Windows client OS's using more than 2GB of memory.
When will this be looked into and/or addressed? What else can I provide to get a resolution on this issue?
comment:8 by , 8 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Without the VBox.log from such a session we can't say anything meaningful.