Opened 16 years ago
Closed 15 years ago
#2473 closed defect (fixed)
Assertion failed in PGMAllPool.cpp(1517) int pgmPoolMonitorInsert(PGMPOOL*, PGMPOOLPAGE*) rc=-1701
Reported by: | vondralbra | Owned by: | |
---|---|---|---|
Component: | VMM | Version: | VirtualBox 2.0.2 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
A 1.5GB RHEL5 guest crashes on a 4GB Host using Ubuntu Intrepid (Kernel 2.6.27-7) during an Oracle installation in the guest machine.
The location of the crash is in pgmPoolMonitorInsert() and the errorcode is -1701(VERR_MM_HYPER_NO_MEMORY) which means that a call to MMHyperAlloc() was not able to allocate any memory although enough cache and swap is available.
There has been some discussion on the issue in the virtualbox-forum in that link: http://forums.virtualbox.org/viewtopic.php?t=10710
The assertion which failed is located here in line 1517 of PGMAllPool.cpp:
1509 rc = PGMHandlerPhysicalRegisterEx(pVM, PGMPHYSHANDLERTYPE_PHYSICAL_WRITE, 1510 GCPhysPage, GCPhysPage + (PAGE_SIZE - 1), 1511 pPool->pfnAccessHandlerR3, MMHyperCCToR3(pVM, pPage), 1512 pPool->pfnAccessHandlerR0, MMHyperCCToR0(pVM, pPage), 1513 pPool->pfnAccessHandlerGC, MMHyperCCToRC(pVM, pPage), 1514 pPool->pszAccessHandler); 1515 /** @todo we should probably deal with out-of-memory conditions here, but for now increasing 1516 * the heap size should suffice. */ 1517 AssertFatalRC(rc);
which means that "rc" is set by either a call to MMHyperAlloc() or a call to pgmHandlerPhysicalSetRamFlagsAndFlushShadowPTs() in PGMAllHandler.cpp
The error occurs on the guest regardless of the size. I tried 900M, 1024M and 1536M.
Very likely this ticket might be a duplicate entry to http://www.virtualbox.org/ticket/1629 but here is no USB-logic involved at all.
Attachments (2)
Change History (6)
by , 16 years ago
Attachment: | orael32-2008-10-22-15-30-50.log added |
---|
comment:1 by , 16 years ago
Further investigation gave that this issue is in 1.6.6 as well as in 2.0.2. After a purge of the virtualbox-2.0 Package I installed the virtualbox-Package 1.6.6 and retried the installation resulting in a GURU-Meditation of the Guest-Machine. This issue is pretty reproducible on this machine.
00:09:03.360 Guest requests mouse pointer integration 00:09:41.837 Guest Log: vboxadd_hgcm_connect: Connected, client ID 2 !!Assertion Failed!! Expression: RT_SUCCESS_NP(rc) Location : /home/vbox/vbox-1.6.6/src/VBox/VMM/VMMAll/PGMAllPool.cpp(1310) int pgmPoolMonitorInsert(PGMPOOL*, PGMPOOLPAGE*) -1701 00:21:46.900 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
The errorcode is the same as in 2.0.2 - just the position in the sourcecode is some other.
comment:2 by , 16 years ago
Results from different memory settings of the guest machine:
- 1536M-RAM Guest: Guest crashes during Installation of Oracle 10.2.0.1/32
- 1024M-RAM Guest: Guest crashes during Installation of Oracle 10.2.0.1/32
- 896M-RAM Guest: Installation of Oracle 10.2.0.1 works (despite the warning of low RAM) but crashes during the 10.2.0.4 patch procedure during "dbua" (which is quite ressource intensive).
- 786M-RAM Guest: Installation of Oracle 10.2.0.1 works (despite the warning of low RAM) and the 10.2.0.4 patch was fine.
The host in question has always been the same and the guest has no USB support at all.
by , 16 years ago
Attachment: | orasles32-2008-10-25-11-12-11.log added |
---|
Error exists still in Virtualbox 2.0.4 - SLES10SP2-Guest using 1024M RAM
Logfile of the crash mentioned in the forum.