Opened 16 years ago
Closed 15 years ago
#4313 closed defect (worksforme)
Host Memory Low error
Reported by: | Torben Nehmer | Owned by: | |
---|---|---|---|
Component: | VMM | Version: | VirtualBox 2.2.4 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
I recently upgraded to VB 2.2.4 and since then I cannot use any(!) VM anymore. I am using a 6 GB Quadcore System, which normally has 2 GB of RAM available. Even a VM set to 1 GB RAM does sometimes not even start. Right now, the VMs do start to a Windows login, but then freeze:
00:00:34.704 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"
When I cannot start the system directly throws a memory related error as well:
00:00:00.620 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={9511bc54-15ee-4ddf-808e-472aba03809c} aComponent={Console} aText={Unknown error creating VM (VERR_NO_MEMORY)} aWarning=false, preserve=false 00:00:00.627 Power up failed (vrc=VERR_NO_MEMORY, rc=E_FAIL (0X80004005))
I am quite sure, that I do have enough memory available. I even stopped the SQL Server (normally running at around 3 GB allocated RAM) to verify this. The task manager normally does not report more then 4 or 4.5 GB of used physical memory.
Any hints would be appreciated. If you need any more information, please let me know.
Attachments (4)
Change History (7)
by , 16 years ago
Attachment: | windows7 - login freeze.log added |
---|
by , 16 years ago
Attachment: | windows7 - startup failure.log added |
---|
by , 16 years ago
Attachment: | windowsXP - login freeze.log added |
---|
by , 16 years ago
Attachment: | windowsXP - startup failure.log added |
---|
comment:1 by , 15 years ago
Component: | other → VMM |
---|
comment:2 by , 15 years ago
comment:3 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
The original reporter replied that he doesn't use VirtualBox any longer.
Please update to VirtualBox 3.0.8 and check if the problem is gone.