Custom Query (16363 matches)
Results (2218 - 2220 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10704 | obsolete | BSOD: SPECIAL_POOL_CORRUPTION_TYPE: 23 | ||
| Description |
BSOD: VirtualBox 4.1.18 for Windows hosts, Win 7 Ultimate 64 Bit host Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
BUGCHECK_STR: 0xC1_23
SPECIAL_POOL_CORRUPTION_TYPE: 23
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: VirtualBox.exe
CURRENT_IRQL: 1
IRP_ADDRESS: fffff980042eaf3b
LAST_CONTROL_TRANSFER: from fffff8000356934a to fffff800034e31c0
STACK_TEXT:
fffff880`27cbb368 fffff800`0356934a : 00000000`000000c1 fffff980`03802fd0 fffff980`03802367 00000000`00530030 : nt!KeBugCheckEx
fffff880`27cbb370 fffff800`035e1fa3 : 00000000`00000000 00000000`00000000 fffff980`042eafa0 fffffa80`21619270 : nt!MiCheckSpecialPoolSlop+0x9a
fffff880`27cbb3b0 fffff800`0360d93b : fffff800`03464000 00000000`20206f49 ffffffff`fff70afa fffffa80`1ffa0280 : nt!MmFreeSpecialPool+0x1d3
fffff880`27cbb4f0 fffff800`034f7ade : 00000000`00000000 fffff980`042eafb0 fffff980`012eaa10 fffff980`0ffeaee0 : nt!ExDeferredFreePool+0xf33
fffff880`27cbb5a0 fffff800`034e6eea : fffff980`042eafb3 00000000`00000001 00000000`00000001 fffff800`0359cdf3 : nt!IopCompleteRequest+0x5ce
fffff880`27cbb670 fffff800`0397f19f : fffff980`042eaee0 fffff980`042eaf00 fffff980`042eae00 00000000`00000000 : nt!IopfCompleteRequest+0x66a
fffff880`27cbb760 fffff880`01baf1f6 : fffff880`27cbb8e8 00000000`00000000 00000000`00000000 fffff980`042eaee0 : nt!IovCompleteRequest+0x19f
fffff880`27cbb830 fffff800`03985c16 : fffff980`042eaee0 00000000`00000002 fffffa80`1d7e8060 fffffa80`18efe398 : VBoxDrv+0x11f6
fffff880`27cbb870 fffff800`037f9717 : fffffa80`1ffa0280 fffff880`27cbbb60 fffffa80`1ffa0280 fffffa80`244d70a0 : nt!IovCallDriver+0x566
fffff880`27cbb8d0 fffff800`037f9f76 : fffff880`03765180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`27cbba00 fffff800`034e2453 : fffffa80`21619270 00000000`04c3fa18 fffff880`27cbba88 fffff800`037e8000 : nt!NtDeviceIoControlFile+0x56
fffff880`27cbba70 00000000`7750138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04c3fb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7750138a
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxDrv+11f6
fffff880`01baf1f6 488b6c2448 mov rbp,qword ptr [rsp+48h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: VBoxDrv+11f6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxDrv
IMAGE_NAME: VBoxDrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fce116c
FAILURE_BUCKET_ID: X64_0xC1_23_VRF_VBoxDrv+11f6
BUCKET_ID: X64_0xC1_23_VRF_VBoxDrv+11f6
Followup: MachineOwner
---------
2: kd> lmvm VBoxDrv
start end module name
fffff880`01bae000 fffff880`01bea000 VBoxDrv (export symbols) VBoxDrv.sys
Loaded symbol image file: VBoxDrv.sys
Image path: \SystemRoot\system32\DRIVERS\VBoxDrv.sys
Image name: VBoxDrv.sys
Timestamp: Tue Jun 05 10:02:20 2012 (4FCE116C)
CheckSum: 00039627
ImageSize: 0003C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
|
|||
| #10705 | obsolete | Portforwarding for NAT cranky about zeroes | ||
| Description |
Hi.. I'm using VB 4.1.18 on MacOSX 10.6.8 with Fedora17 x86_64 as the guest. In order to forward port 2222 on the Mac to port 22 on the guest, I clicked on 'settings' for the guest in the VB manager, picked 'network', picked 'port forwarding', clicked on '+', and entered:
The first time I pressed 'OK', VB said 'Zeroes are not allowed'. The second time I pressed 'OK', it worked, and everything seems fine in all respects. Could you get rid of the bogus warning message? Thanks |
|||
| #10706 | obsolete | Kernel panic with physical disk access | ||
| Description |
I'm using Virtual Box in order to run a NAS on Debian (it is OpenmediaVault, but I don't think it is relevant). I have a "metal" Openmediavault system and I attach a drive to either system, metal or VM. The host is Windows7 Pro 64 SP1 and last version of Virtual Box (4.1.18 r78361)
So I have a SATA physical disk attached to this VM. I created a vmdk file using
"C:\Program Files\Oracle\VirtualBox\VBoxManage" internalcommands createrawvmdk -filename "D:\Users\me\VirtualBox VMs\DD1.vmdk" -rawdisk The drive does not contain the OS. It is a logical volume, (see lvm2 on Linux litterature), which contains an XFS file system
From the guest system point of view, it is very simple :
I experience kernel panic (see attached screen shot), which becomes almost systematic. There are two possibilities :
I noticed the success ratio is better when I remove the SATA controler, recreate it and attach again the physical disk. I opened a thread on Linux guest forum https://forums.virtualbox.org/viewtopic.php?f=3&t=50135 where you can see kernel panic screen shot when the VM starts, I see that VirtualBox takes a handle on Harddisk1, when there is a kernel panic, it does not, so it may be an access problem to the hard disk. But I see no process having a handle on the raw disk I do not have this problem on my home PC with WIndows 7 Home Premium and the same VM As suggested by moderator Perryg, I create this ticket. Please find the log file |
|||

