Custom Query (16363 matches)
Results (1900 - 1902 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3403 | fixed | Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND) when starting a VM on Linux 2.6.29-rc6 | ||
| Description |
When starting any VM (new or old) on vbox 2.1.2/2.1.4 I get a dialog box that says the following Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).
Unknown error creating VM (VERR_SYMBOL_NOT_FOUND).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {e3c6d4a1-a935-47ca-b16d-f9e9c496e53e}
This is followed by a log in my /home Log created: 2009-02-20T15:17:05.822351000Z Executable: /opt/VirtualBox/VirtualBox Arg[0]: /opt/VirtualBox/VirtualBox Arg[1]: -comment Arg[2]: WinXP Arg[3]: -startvm Arg[4]: 6d5f33b5-8fd1-4685-92e7-70f21442f0f4 1: SUPR0AbsIs64bit 2: SUPR0Abs64bitKernelCS 3: SUPR0Abs64bitKernelSS 4: SUPR0Abs64bitKernelDS 5: SUPR0AbsKernelCS 6: SUPR0AbsKernelSS 7: SUPR0AbsKernelDS 8: SUPR0AbsKernelES 9: SUPR0AbsKernelFS 10: SUPR0AbsKernelGS 11: SUPR0ComponentRegisterFactory 12: SUPR0ComponentDeregisterFactory 13: SUPR0ComponentQueryFactory 14: SUPR0ObjRegister 15: SUPR0ObjAddRef 16: SUPR0ObjAddRefEx 17: SUPR0ObjRelease 18: SUPR0ObjVerifyAccess 19: SUPR0LockMem 20: SUPR0UnlockMem 21: SUPR0ContAlloc 22: SUPR0ContFree 23: SUPR0LowAlloc 24: SUPR0LowFree 25: SUPR0MemAlloc 26: SUPR0MemGetPhys 27: SUPR0MemFree 28: SUPR0PageAlloc 29: SUPR0PageFree 30: SUPR0Printf 31: SUPR0GetPagingMode 32: SUPR0EnableVTx 33: RTMemAlloc 34: RTMemAllocZ 35: RTMemFree 36: RTMemRealloc 37: RTR0MemObjAllocLow 38: RTR0MemObjAllocPage 39: RTR0MemObjAllocPhys 40: RTR0MemObjAllocPhysNC 41: RTR0MemObjAllocCont 42: RTR0MemObjEnterPhys 43: RTR0MemObjLockUser 44: RTR0MemObjMapKernel 45: RTR0MemObjMapKernelEx 46: RTR0MemObjMapUser 47: RTR0MemObjAddress 48: RTR0MemObjAddressR3 49: RTR0MemObjSize 50: RTR0MemObjIsMapping 51: RTR0MemObjGetPagePhysAddr 52: RTR0MemObjFree 53: RTProcSelf 54: RTR0ProcHandleSelf 55: RTSemFastMutexCreate 56: RTSemFastMutexDestroy 57: RTSemFastMutexRequest 58: RTSemFastMutexRelease 59: RTSemEventCreate 60: RTSemEventSignal 61: RTSemEventWait 62: RTSemEventWaitNoResume 63: RTSemEventDestroy 64: RTSemEventMultiCreate 65: RTSemEventMultiSignal 66: RTSemEventMultiReset 67: RTSemEventMultiWait 68: RTSemEventMultiWaitNoResume 69: RTSemEventMultiDestroy 70: RTSpinlockCreate 71: RTSpinlockDestroy 72: RTSpinlockAcquire 73: RTSpinlockRelease 74: RTSpinlockAcquireNoInts 75: RTSpinlockReleaseNoInts 76: RTTimeNanoTS 77: RTTimeMillieTS 78: RTTimeSystemNanoTS 79: RTTimeSystemMillieTS 80: RTThreadNativeSelf 81: RTThreadSleep 82: RTThreadYield 83: RTLogDefaultInstance 84: RTMpCpuId 85: RTMpCpuIdFromSetIndex 86: RTMpCpuIdToSetIndex 87: RTMpIsCpuPossible 88: RTMpGetCount 89: RTMpGetMaxCpuId 90: RTMpGetOnlineCount 91: RTMpGetOnlineSet 92: RTMpGetSet 93: RTMpIsCpuOnline 94: RTMpIsCpuWorkPending 95: RTMpOnAll 96: RTMpOnOthers 97: RTMpOnSpecific 98: RTPowerNotificationRegister 99: RTPowerNotificationDeregister 100: RTLogRelDefaultInstance 101: RTLogSetDefaultInstanceThread 102: RTLogLogger 103: RTLogLoggerEx 104: RTLogLoggerExV 105: RTLogPrintf 106: RTLogPrintfV 107: AssertMsg1 108: AssertMsg2 VMMR0.r0 is importing g_SUPGlobalInfoPage which we couldn't find I am using virtualbox binaries install on Gentoo w/ kernel 2.6.29-rc5 xorg-server 1.5.3-r2, libsdl 1.2.13-r1 Not sure what the resolution is. |
|||
| #3404 | fixed | date information corrupted on files ending in 'inp' | ||
| Description |
From within the Guest OS (WinXP), if a file that ends in 'inp' is created/renamed/modified in a shared directory then the date information on that file is mangled. For example, a file named 'test.inp' and a file named 'testinp' both exhibit this behavior. However, there is no problem with a file named 'inp.txt' From the Guest, the date of the file appears to be "Thursday, July 21, 2185, 6:34:33 PM" From the Host, the date of the file appears to be "2185-07-21 19:34" (In some cases, the date has appeared as May 1913, however this is not consistent and may involve some other program operating on the file after the date is corrupted) If a file that ends in 'inp' already exists in the shared directory, then its date is not modified. However, an 'inp' file that is created in the Host OS while the Guest OS is running will be modified when the Guest OS refreshes its file view. The behavior is consistent and repeatable. |
|||
| #3405 | fixed | Streets and Trips 2007 won't install OS X Client | ||
| Description |
Streets and Trips 2007 installed will not run on OS X client from CD and when copied to C:. Following Windows Installer error: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. |
|||

