Page 1 of 1

Failed to map a memory object.

Posted: 3. Feb 2011, 02:30
by mikeubell
I am running VB 4.0.2 on Windows XP. While running a Ubuntu 10.10 client the VM crashed. The end of the log says:

02:40:10.819 AssertLogRel E:\tinderbox\win-rel\src\VBox\VMM\VMMAll\PGMAllPhys.cpp(1929) PGMPhysRead: <NULL>
02:40:10.819 pgmPhysGCPhys2CCPtrInternalReadOnly failed on 000000005baf3000 / A--:RAM:0000ce51a000:00c780f:-0000 -> VERR_MAP_FAILED
02:40:10.841 AssertLogRel E:\tinderbox\win-rel\src\VBox\VMM\VMMR3\PGMPhys.cpp(4306) PGMR3PhysTlbGCPhys2Ptr: RT_SUCCESS_NP(rc2)
02:40:10.841 VERR_MAP_FAILED (-75) - Failed to map a memory object.

The first two lines are previously repeated several times.

What to do next?

Re: Failed to map a memory object.

Posted: 26. Mar 2011, 04:49
by wacher
I have similar problem, i use 4.0.4
I opened a ticket http://www.virtualbox.org/ticket/8630, please add your experiences if you have any.

Re: Failed to map a memory object.

Posted: 20. Apr 2011, 13:53
by acy
I have been experiencing a similar problem with my VM's as well. It does not affect my 2 Windows Xp or Ubuntu VM's which are configured 512MB each. My Windows 2008 VM configured with 2GB memory clocks up completely within hours in some cases while other VM's continue to run. I have tried changing settings and OS

-Windows 2008 (32 and 64 bit) and Windows 2008 R2 64 bit
- PAE settings on or off
- APIC I/O disabled for 32bit Windows 2008
- 1 or 2 CPU configuration
- Nested Pagin on or off

None of these seems to have made any difference. This problem started after upgrading to Virtualbox 4.0.2 as all the VM's worked without problem before this.

I have attached the log for the latest crash.

The crashes have caused data corruption in the past so I hope the cause can be identified and corrected quickly.