Custom Query (16363 matches)
Results (1399 - 1401 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2472 | fixed | Display mangles and Windows XP guest freezes | ||
| Description |
I'm running Windows XP guest on an Ubuntu host with Virtual box 2.0.2. I've installed guest additions, and after that I occasionally get the display mangled (mostly black and with some random colors), and the guest won't resume functioning. Unfortunately I don't know how to reproduce it. However I've noticed that this is mainly observed after some user interaction -- say I moved in/out of the full-screen. |
|||
| #2473 | fixed | Assertion failed in PGMAllPool.cpp(1517) int pgmPoolMonitorInsert(PGMPOOL*, PGMPOOLPAGE*) rc=-1701 | ||
| 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. |
|||
| #2475 | fixed | VBoxSDL.so is NOT statically linked against libSDL on Solaris 10 x86 => Fixed in next version | ||
| Description |
Hello.
In the Solaris x86 version (VirtualBox-2.0.2-36488-SunOS_x86.tar.gz), VBoxSDL.so is dynamically linked against libSDL-1.2.so.0 which is not included in Solaris 10 (u5).
# ldd VBoxSDL.so
libX11.so => /usr/lib/libX11.so
[ ... ]
VBoxXPCOM.so => /opt/VirtualBox/VBoxXPCOM.so
libSDL-1.2.so.0 => (file not found)
libstdc++.so.6 => /usr/sfw/lib/libstdc++.so.6
[ ... ]
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
#
starting of VBoxSDL will break with: # ./VBoxSDL
VBoxSDL: supR3HardenedMainGetTrustedMain: dlopen("/opt/VirtualBox/VBoxSDL.so",)
failed: ld.so.1: VBoxSDL: fatal: libSDL-1.2.so.0: open failed: No such file or directory
#
VBoxSDL.so should be statically linked against libSDL.a for the Solaris 10 x86 OS. |
|||

