Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Doesn’t work with VirtualBox
- This topic has 2 replies, 2 voices, and was last updated 14 years, 10 months ago by
Anonymous.
-
AuthorPosts
-
June 30, 2010 at 15:06 #207
blackjackshellac
ParticipantInstall VirtualBox 3.2.6 r63112 on Windows7 x64 Ultimate.
Download this package: http://downloads.sourceforge.net/project/virtualkd/virtualkd/2.3/VirtualKD-2.3.zip.
Rename VBoxDD.dll to VBoxDD0.dll and copy x64 VBoxDD.dll in VirtualBox folder.
Crashes (Acess Violation second chance exception) when starting a guest in VirtualBox.exe.
Replace VBoxDD.dll with patch from http://virtualkd.sysprogs.org/VBoxPatch-3.1.0.zip.
Still crashes when starting a guest VirtualBox.exe.
Has this been tested with latest VirtualBox?Child-SP RetAddr Call Site
00000000`03c6f7a8 00000000`0720bfa5 0x0
00000000`03c6f7b0 000007fe`f252947a VBoxDD0!VBoxUsbRegister+0xaad5
00000000`03c6f8b0 00000001`800b46d1 VBoxDD!ConstructOverride+0x2a
00000000`03c6f910 00000001`8004c0aa VBoxVMM!PDMR3DeviceDetach+0x881
00000000`03c6fbf0 00000001`80005da4 VBoxVMM!PDMR3Init+0xaa
00000000`03c6fc70 00000001`80008d54 VBoxVMM!VMR3HotPlugCpu+0x294
00000000`03c6fce0 00000001`80033b0d VBoxVMM!VMR3SetRuntimeErrorWorker+0x5a4
00000000`03c6fd90 00000001`80034298 VBoxVMM!VMR3ReqWait+0x25d
00000000`03c6fe00 00000001`8004d5e7 VBoxVMM!VMR3ReqProcessU+0x128
00000000`03c6fe40 00000000`003601ef VBoxVMM!VMR3WaitU+0x497
00000000`03c6fea0 00000000`003ab658 VBoxRT!RTThreadFromNative+0x52f
00000000`03c6fed0 00000000`744337d7 VBoxRT!RTSemMutexCreate+0x198
00000000`03c6ff00 00000000`74433894 MSVCR80!_callthreadstartex+0x17
00000000`03c6ff30 00000000`7711f56d MSVCR80!_threadstartex+0x84
00000000`03c6ff60 00000000`77253021 kernel32!BaseThreadInitThunk+0xd
00000000`03c6ff90 00000000`00000000 ntdll!RtlUserThreadStart+0x1dNovember 26, 2010 at 00:40 #1452Anonymous
ParticipantThe same problem with host: win7/x86 virtualbox 3.1.6
December 25, 2010 at 06:24 #1453Anonymous
ParticipantI thought I had the same problem with VirtualBox 3.2.12 r68302 until I realised that I needed to use the latest version of VirtualKD (2.5.1) rather than the version that ships with VisualDDK.
2.5.1 introduced support for VirtualBox 3.2.x
By downloading the newer version (2.5.1) of VirtualKD and following the instructions in the readme.txt file I managed to patch virtuall box successfully on the host (by copying the new VBoxDD.dll) and install VirtualKD on the guest.
The apparent hang of the guest at startup in my case was simply that it was waiting for the kernel debugger to attach. Make sure you have windbg or kd running on the correct pipe before you let the guest boot.
-
AuthorPosts
- You must be logged in to reply to this topic.