Hi VBox experts,
I have been happily using VBox for a while, then winXP guest suddenly stopped working tonight. Below is the log, and it looks like suffering memory allocation issue, which I saw before I made this work. As I don't remember any change to VBox setting recently, I am left clueless. Please review the log below, and suggest me what to try. Thank you.
VBox winXP stopped working - win7 host
-
jheoaustin
- Posts: 7
- Joined: 12. Mar 2012, 01:37
VBox winXP stopped working - win7 host
- Attachments
-
vblog.txt- (72.64 KiB) Downloaded 5 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: VBox winXP stopped working - win7 host
Most likely the cause is not something you are doing inside VirtualBox, it's some other application which is allocating and hogging memory. Look at your host process list for a memory hog. Google Chrome (actually the crash handler / reporter) is known as one of the usual suspects.VBox.log wrote: 00:00:08.483 Guest reported fixed hypervisor window at 0x00000000f6400000 (size = 0xc00000, rc = VINF_SUCCESS)
00:00:09.604 PGM: Failed to procure handy pages; rc=VERR_NO_MEMORY rcAlloc=VINF_SUCCESS rcSeed=VINF_SUCCESS cHandyPages=0x1f
00:00:09.604 cAllPages=0x444a5 cPrivatePages=0x12212 cSharedPages=0x0 cZeroPages=0x32290
00:00:09.604 GMM: Statistics:
00:00:09.604 Allocated pages: ddad
00:00:09.604 Maximum pages: 4009e
00:00:09.604 Ballooned pages: 0
00:00:09.605 PGM: Failed to procure handy pages; rc=VERR_NO_MEMORY rcAlloc=VINF_SUCCESS rcSeed=VINF_SUCCESS cHandyPages=0x1f
00:00:09.605 cAllPages=0x444a5 cPrivatePages=0x12212 cSharedPages=0x0 cZeroPages=0x32290
00:00:09.605 GMM: Statistics:
00:00:09.605 Allocated pages: ddad
00:00:09.605 Maximum pages: 4009e
00:00:09.605 Ballooned pages: 0
00:00:09.605 VM: Raising runtime error 'HostMemoryLow' (fFlags=0x2)
00:00:09.605 AssertLogRel D:\tinderbox\win-4.1\src\VBox\VMM\VMMR3\VMM.cpp(1680) VMMR3EmtRendezvous: !pVCpu->vmm.s.fInRendezvous
00:00:09.605 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:00:09.605 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.