文件列表:

VirtualBox\kdclient.dll (189440, 2010-07-12)
VirtualBox\kdclient64.dll (226304, 2010-07-12)
VirtualBox\target\kdpatch.reg (148, 2010-07-12)
VirtualBox\target\vminstall.exe (306840, 2010-07-12)
VirtualBox\target\x64\kdpatch.sys (73880, 2010-07-12)
VirtualBox\target\x64\kdvm.dll (20120, 2010-07-12)
VirtualBox\target\x86\kdpatch.sys (23192, 2010-07-12)
VirtualBox\target\x86\kdvm.dll (17048, 2010-07-12)
VirtualBox\VirtualBox\x64\VBoxDD.dll (144384, 2010-07-12)
VirtualBox\VirtualBox\x86\VBoxDD.dll (119808, 2010-07-12)
VirtualBox\vmmon.exe (172544, 2010-07-12)
VirtualBox\vmmon64.exe (214016, 2010-07-12)
VirtualBox\vmxpatch.exe (56832, 2010-07-12)
VirtualBox\vmxpatch64.exe (58368, 2010-07-12)
VirtualBox\target\x64 (0, 2011-08-25)
VirtualBox\target\x86 (0, 2011-08-25)
VirtualBox\VirtualBox\x64 (0, 2011-08-25)
VirtualBox\VirtualBox\x86 (0, 2011-08-25)
VirtualBox\target (0, 2011-08-25)
VirtualBox\VirtualBox (0, 2011-08-25)
VirtualBox (0, 2011-08-25)

VirtualKD - Kernel Debugger extension for VMWare and VirtualBox Version 2.5.1 http://virtualkd.sysprogs.org/ Copyright (c) Ivan Shcherbakov aka Bazis, 2009 [ivan@sysprogs.org] !!!Attention!!! VM installation is now automatic. Just run the target\VMINSTALL.EXE on your guest OS!!! See http://VirtualKD.sysprogs.org/ for latest notes & installation guide OVERVIEW The VirtualKD project allows speeding up Windows kernel module debugging using VMWare virtual machine. If you have ever noticed that the standard debugging over virtual COM port is irritatingly slow, this software is for you! Normally, debugging over a virtual COM port involves the following scheme: * Windows uses a virtual COM port to exchange data with host * WinDBG/KD uses a named pipe provided by VMWare to communicate with debugging OS The weakest link in this scheme is the virtual COM port, as its speed is limited to 115200 baud, i.e. around 10 KB/s. VirtualKD replaces the virtual COM port-related functinality, raising the exchange rate up to 6 MB/s. Basically, VirtualKD consists of a Windows KD extension DLL and a patch to VMWare process, that creates named pipes on host. COMPATIBILITY VirtualKD supports both x86 and x*** guest operating systems and was tested with the following OSes: * Windows Vista 32bit * Windows XP 32bit * Windows XP ***bit * Windows 7 32bit * Windows 7 ***bit VMWare: all modern versions are supported. The following versions were tested: * VMWare Server 1.0.5 * VMWare Server 2.0.0 * VMWare Workstation 6.5.1 VirtualBox: the latest 3.2 branch is supported. You can rebuild VirtualKD from sources using VirtualBox headers to support other versions. The following versions were tested: * VirtualBox 3.0.4 * VirtualBox 3.1.6 * VirtualBox 3.2.6 VirtualKD supports ***-bit host and ***-bit versions of VMWare. INSTALLATION Starting from version 2.1, VirtualKD can be automatically installed on the virtual machine by running VMINSTALL.EXE on it. However, it can also be installed manually using 2 different ways: A) Dynamic patching (not recommended). Copy both KDPATCH.SYS and KDVM.DLL to SYSTEM32\DRIVERS directory of your virtual machine (yes, both DLL and SYS in the same place) and apply the KDPATCH.REG file (or manually create a legacy driver running KDPATCH.SYS). Then, perform the following sequence: 1) Start the virtual machine 2.VMWare) BEFORE OS starts to load, patch the VMWare process on host side using VMXPATCH.EXE or VMMON.EXE (see below) 2.VirtualBox) Rename VBoxDD.dll in VirtualBox directory to VBoxDD0.dll. Copy VBoxDD.DLL from VirtualKD instead of original VBoxDD.dll 3) Start your virtual Windows in a normal debug mode with a virtual COM port 4) Ensure that WinDBG establishes connection (our driver is not involved now) 5) Let the OS boot 6) Wait for the KDPATCH.SYS driver to load (if you set it to manual mode, run "net start kdpatch"). This will redirect all debugging activity from the COM port simulated by VMWare to our fast debugging interface (VMWare needs to be already patched at this moment). 7) Start the WinDBG or KD debugger. The pipe name for the fast debugging is the following: \\.\pipe\kd_, when your VM is located at X:\something\\filename.vmx 8) You can close the first instance of WinDBG. Alternatively, you can stop the KDPATCH.SYS driver at any moment to direct debug activity back to the VMWare COM port. This method is useful if you want to play with the VirtualKD sources and to load different versions of KDVM.DLL without rebooting the virtual machine. Just start the patcher service, and the KDVM.DLL is used instead of KDCOM.DLL. Stop it and KDCOM.DLL gains control back. B) Static patching (recommended) 0.VirtualBox) Rename VBoxDD.dll in VirtualBox directory to VBoxDD0.dll. Copy VBoxDD.DLL from VirtualKD instead of original VBoxDD.dll 1) Copy KDVM.DLL to SYSTEM32 directory of your guest OS. There should already exist KDCOM.DLL and KD1394.DLL files. --- For XP --- 2) Open your boot.ini file. If you are using the COM debugging, you should have a line like this: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /DEBUG /DEBUGPORT=COM1 3) Change it to this: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /DEBUG /DEBUGPORT=VM --- For Vista/Win7 --- 2,3) Run the following command line: bcdedit /set dbgtransport kdvm.dll --- 4) Reboot your virtual machine and wait for the OS selection dialog. 5.VMWare) Patch VMWare executable using VMXPATCH.EXE or VMMON.EXE (see below). 6) Start WinDBG or KD. Use \\.\pipe\kd_ as pipe name (see above). 7) Start your guest OS The /DEBUGPORT=VM parameter in boot.ini instructs Windows to use the KDVM.DLL file as the packet layer driver for kernel debugging. This is more flexible than patching KDCOM.DLL, as it does not require booting in COM debug mode. In Vista/Win7 this functionality is achieved by setting the "dbgtransport option via BCDEDIT. PATCHING To patch the VMWare executable you can use the VMXPATCH.EXE. Just run it and it will find the first instance of VMWare running on your machine and patch it by loading KDCLIENT.DLL in it. You can then choose to unpatch the VM and KDCLIENT.DLL will be unloaded. This can be useful while playing with the sources. If you are using VirtualBox, no patching is required. You need to rename the original VBoxDD.DLL to VBoxDD0.DLL and copy VBoxDD.DLL from VirtualKD instead of the original one. This ensures that VirtualKD client part is loaded correctly. However, normally it is recommended to use the VMMON.EXE application. It will automatically detect VMWare virtual machines and patch them. It can even start the WinDBG or KD automatically when a VirtualKD-aware OS is detected on the virtual machine, and close them when VM stops. For VirtualBox, VMMON.EXE does not perform any patching, it simply displays statistic info. BUGS None known in v2.0. If you find any, write me an e-mail. TROUBLESHOOTING If something goes wrong, I strongly recommend you to download the sources from SourceForge and see everything in a debugger. Alternatively, you can attach Visual Studio debugger to VMWARE-VMX.EXE process BEFORE patching it and observe the debug output. TWEAKING You can modify some parameters in registry under SOFTWARE\BazisSoft\VirtualKD\Patcher 1) AllowPatchingAtTableStart. Set it to 0 if your VMWare crashes when being patched. 2) AllowReplacingFirstCommand. Set it to 1 if patching fails (and debug output indicates something like "0 free entries"). 3) DefaultPatchingAtTableStart. You can try setting this to increase the performance (just a bit), but in can make VMWare crash on patching. Feel free to try ;) Additionally, you can set the WaitForOS to 0 in VirtualKD\Monitor to let the debugger be started immediately when a VM is detected (without waiting for OS to load). SOURCE STRUCTURE The information about source code structure and some hints for experimenting will be soon published at http://VirtualKD.sysprogs.org/. CHANGE LOG v1.0 Initial version v1.1 Fixed handler loss after Virtual Machine reset Fixed bug with VMWare hanging when no debugger is connected Added patcher/packet level log displaying in VMMON Added support for KDCLIENT.DLL unloading from VMMON Added advanced statistics reporting to VMMON Added permissive SECURITY_ATTRIBUTES to statistics-related objects to support non-admin VMWare instances Added debugger command line customization Added proxy mode support for debug VMMON builds Added TraceAssist feature Implemented buffered VMWare GuestRPC resulting in ~1.7x communication speedup v1.2 (Only host-side part changed) Fixed rare bug, when disconnecting debugger in the middle of a KdSendPacket() call caused hanging Reduced CPU usage from 100% to 0% when a VM is active and no debugger is connected Added workaround for truncated Driver Verifier messages Added on-demand packet logging feature for easy packet-level KD protocol analyzis Added API for detecting & patching VMs to KDCLIENT.DLL to support VisualDDK integration Pipe name is now generated based on VMWARE-VMX.EXE command line, instead of current directory (fix for rare "kd_" pipes) Added support for sending generated 'Target OS Shutdown' packet when VM is stopping to force debugger to disconnect Added ",reconnect" option to WinDbg command line, instructing it to reconnect a pipe, when it is closed (Due to 2 previous features, debugger does not need to be restarted when a VM is restored from a snapshot, while OS is running) v1.3 (Only host-side part changed) Added support for ***-bit host operating systems and ***-bit versions of VMWare. v2.0 (KDVMWare was renamed to VirtualKD) Added support for VirtualBox v2.1 Added support for Windows 7 host and guest machines Added test signature to KDVM.DLL allowing it to run on Vista x*** in TESTSIGNING mode Added automatic guest machine installer v2.2 Improved integration with VisualDDK Added support for VMWARE-VMX-DEBUG.EXE etc. v2.3 Fixed memory leak in VMMON Added support for patching VMs from non-administrator accounts via IPC with VMMON Fixed bug when only first running VM was reported Added support for VirtualBox 3.1.x v2.4 Fixed compatibility with UAC (.vmpatch files are now saved to Application Data) v2.5 Added "instant break" feature, reducing debugger break-in time to zero when using VisualDDK Added support for restoring VM (VirtualBox/VMWare) to last snapshot from VMMON/VisualDDK v2.5.1 Added support for VirtualBox 3.2.x THANKS I would like to thank the following people for making the creation of this tool possible: * Ken Johnson [http://www.nynaeve.net] for the idea (VMKD project). * OpenVMTools team [http://sourceforge.net/projects/open-vm-tools] * Tomasz Nowak [http://undocumented.ntinternals.net/] * MS and VMWare for creating (relatively) scalable and flexible architectures

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：