May be that will add some food for thought for those who knows how it works inside...
Several (not all) logs created when guest OS crashed contained lines similar to this:
Code: Select all
00:00:40.949 pgmr3PhysGrowRange: out of memory. pause until the user resumes execution.
00:00:40.949 Changing the VM state from 'RUNNING' to 'SUSPENDED'.
00:00:45.977 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"
What I see:
1) Machine crashes without any dialog box telling that VM is paused. After crash VM is in "Aborted" state.
2) I watched "Task Manager"'s "Physical Memory (K)" allocations and particularly "Available" and noticed that the crash occurs when it becomes low.
But:
1) I started VM at the time when host OS has 270,000 KiB available. Guest OS is configured to have only 192 MiB "Base Memory". And apparently VB wants to acquire more then (or around) 270,000 KiB. Why?
2) Why it's the problem (if it is the problem here)? That's what WXP memory management is for - reallocate physical memory using paging file, and at that time of VB crash computer has a plenty of free memory in "Commit Charge (K)".
I hope this will help somehow to troubleshoot...