Custom Query (16363 matches)
Results (2194 - 2196 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10645 | obsolete | Host out of space error and truncated .vbox files | ||
| Description |
If the host runs out of space, one of the VBoxHeadless decides to suspend itself due to that fact, and subsequent attempts to resume attempts to resume or restart the guest without realizing that there was an out of space condition, the .vbox file and its backup .vbox-prev are both truncated. It is useless to make a backup of a truncated file and overwriting a known good file. Adding some code to verify that the file to be backed-up is a fully understandable by the program would avoid this issue. Along the same lines, are runtime errors reported back via webservices? Thanks. |
|||
| #10646 | obsolete | BSOD on Windows - DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION | ||
| Description |
Loading Dump File [C:\Users\cliffje\Desktop\MEMORY\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: SRV*c:\symdownstream*http://msdl.microsoft.com/download/symbols;srv*c:\symdownstream*http://supimages1/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 2600.xpsp_sp3_gdr.120411-1615 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Mon Jun 4 01:27:31.812 2012 (UTC - 4:00) System Uptime: 0 days 8:29:41.596 0: kd> !analyze -v *
* DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6) N bytes of memory was allocated and more than N bytes are being referenced. This cannot be protected by try-except. When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 8f627000, memory referenced Arg2: 00000000, value 0 = read operation, 1 = write operation Arg3: b1f676af, if non-zero, the address which referenced memory. Arg4: 00000000, (reserved) Debugging Details: OVERLAPPED_MODULE: Address regions for 'VMMR0' and 'kmixer.sys' overlap READ_ADDRESS: 8f627000 Special pool FAULTING_IP: VMMR0!vmmR0LoggerWrapper+134d b1f676af 8b01 mov eax,dword ptr [ecx] MM_INTERNAL_CODE: 0 IMAGE_NAME: VMMR0.r0 DEBUG_FLR_IMAGE_TIMESTAMP: 4fbb8fc7 MODULE_NAME: VMMR0 FAULTING_MODULE: b1f1d000 VMMR0 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD6 PROCESS_NAME: VirtualBox.exe TRAP_FRAME: b38eca34 -- (.trap 0xffffffffb38eca34) ErrCode = 00000000 eax=860fe804 ebx=00000020 ecx=8f627000 edx=860fe844 esi=2f00a8c0 edi=8f626f80 eip=b1f676af esp=b38ecaa8 ebp=b38ecaac iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 VMMR0!vmmR0LoggerWrapper+0x134d: b1f676af 8b01 mov eax,dword ptr [ecx] ds:0023:8f627000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 805203ae to 804f9f5f STACK_TEXT: b38ec9b4 805203ae 00000050 8f627000 00000000 ntKeBugCheckEx+0x1b b38eca1c 80544600 00000000 8f627000 00000000 ntMmAccessFault+0x9a8 b38eca1c b1f676af 00000000 8f627000 00000000 nt!KiTrap0E+0xd0 WARNING: Stack unwind information not available. Following frames may be wrong. b38ecaac b1f67b44 8f627000 860fe844 00000004 VMMR0!vmmR0LoggerWrapper+0x134d b38ecacc b1f68e53 9bc6ae90 9bc6aed4 860fe844 VMMR0!vmmR0LoggerWrapper+0x17e2 b38ecaf0 b1f68ea2 860fe836 860fe828 00000806 VMMR0!vmmR0LoggerWrapper+0x2af1 b38ecb04 b1f69e51 00000000 b38ecb3a fffffffd VMMR0!vmmR0LoggerWrapper+0x2b40 b38ecb6c b1f6a050 8ffe0002 92e04cc0 b38ecb9c VMMR0!IntNetR0IfSend+0x101 b38ecb7c b1f339d9 92e04cc0 90836fec 0000003c VMMR0!IntNetR0IfSendReq+0x20 b38ecb9c b1f33caa 00000000 00000000 92e04cc0 VMMR0!VMMR0EntryFast+0xae9 b38ecbd4 b6749a6b 8613f000 fffffffd 00000032 VMMR0!VMMR0EntryEx+0xaa b38ecc04 b6744148 0022801c 99188f68 92e04cc0 VBoxDrv+0x6a6b b38ecc24 b6744547 99188f68 92e04cc0 942b2f68 VBoxDrv+0x1148 b38ecc40 804ef1a9 99188eb0 942b2f68 806e7410 VBoxDrv+0x1547 b38ecc50 8057f9a0 942b2fd8 92550f90 942b2f68 ntIopfCallDriver+0x31 b38ecc64 8058082f 99188eb0 942b2f68 92550f90 ntIopSynchronousServiceTail+0x70 b38ecd00 80579292 00002748 00000000 00000000 ntIopXxxControlFile+0x5c5 b38ecd34 8054168c 00002748 00000000 00000000 ntNtDeviceIoControlFile+0x2a b38ecd34 7c90e514 00002748 00000000 00000000 ntKiFastCallEntry+0xfc 029cfc4c 00000000 00000000 00000000 00000000 0x7c90e514 STACK_COMMAND: kb FOLLOWUP_IP: VMMR0!vmmR0LoggerWrapper+134d b1f676af 8b01 mov eax,dword ptr [ecx] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VMMR0!vmmR0LoggerWrapper+134d FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0xD6_VMMR0!vmmR0LoggerWrapper+134d BUCKET_ID: 0xD6_VMMR0!vmmR0LoggerWrapper+134d Followup: MachineOwner 0: kd> lmv m VMMR0 start end module name b1f1d000 b1f91000 VMMR0 (export symbols) VMMR0.r0
0: kd> lmv m VBoxDrv start end module name b6743000 b676e000 VBoxDrv (no symbols)
|
|||
| #10650 | obsolete | Solaris 10 Host reboot - after kernel panic... | ||
| Description |
After patching our Solaris System 10 with the actual patch cluster (21.5.2012) and updating VirtualBox to version 4.1.16 our server crashes. In the system messages we always find the attached message ahead of the crash. The referenced CPU number varies and so do the addresses. But the rest is 'stable'. Since January we used VirtualBox v4.1.8 without any crashes. And after having troubles with version 4.1.16 I reinstalled v4.1.8 but the crashes persist. System is a SunFire X4600M2 with 8 sockets (Opteron 8356) and 256GB ECC memory. No hardware changes between the running and the crashing system. The guest systems did not change (predominant is WinXP, but linux systems are also running -- sometimes). The logfiles of the users VMs do not show additional messages. It does not seem to be load-dependent - right now only a small number of users is working on the system (load < 20%). Did somebody else experience this? Any ideas? Please let me know, if you need additional logfiles, stats or data. |
|||

