I am facing severe problem,while opening Virtualbocx through my Windows 7 interface. I am repeatedly shown error of "guru meditation" of no tbeing able to allocate memory & else (given in attachment).
Thoug sometimes, once in a while the virtual system(XP loaded on virtual machine) runs propertly also, inspite of same system settings. I am not able to understand. Kindly Help....
vbox.log wrote:
00:00:38.652443 Host RAM: 1640MB total, 826MB available
...
00:00:43.058551 RamSize <integer> = 0x0000000025b00000 (632 291 328, 603 MB)
00:00:43.059820 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
...
00:04:35.377526 VM: Raising runtime error 'HostMemoryLow' (fFlags=0x2)
00:04:35.626891 AssertLogRel D:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\VMM.cpp(1756) int __cdecl VMMR3EmtRendezvous(struct VM *,unsigned int,int (__cdecl *)(struct VM *,struct VMCPU *,void *),void *): !pVCpu->vmm.s.fInRendezvous
00:04:35.778024 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"
00:04:36.825037 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.
Your host is seriously underpowered for this VM. In fact it's underpowered even just for running the Win7-64bit host OS alone. You could try reducing the VM RAM to 256MB and the VRAM to 32MB.
But how could ( Process ) this be done, as there is a serious chance of getting the Virtual Machine getting corrupted on changine the ram size. In fact previously my whole data in VM got corrupted on increasing the VM disc size, & now I fear, if any modification may result in the same.
Thx & Rgds
Nitin
Shut down the VM and reduce the RAM and display RAM sizes in the VM settings. You must know how this is done since you've clearly been "tuning" the RAM already. Nothing can be corrupted. But, performance is likely to be poor since your host simply doesn't have enough spare resources for a VM to exploit.
If the guest works on 256MB/32MB then you could try tweaking it up, to 400MB/32MB say. But, avoid "tuning" to get the maximum RAM, because any slight change in the host will cause the VM to fail again.
VBox.log