VisualDDK 1.5 VMWare 7 Windows 7 x64 Issue Attaching to XP 3

[Driver N00b]

VisualDDK 1.5 VMWare 7 Windows 7 x64 Issue Attaching to XP 32 bit Kernel

Debugging Issues

I am new at this but was really excited to see there was a Visual Solution to developing Drivers. I have followed all of the steps as best i can but cannot connect to the Windows XP Professional running on VMWare. Can someone check these steps to see if i have done everything correctly.

Environment

Windows 7 x64

VisualDDK 1.5

WDK 7600.16385.1

Debugging tools for windows version 6.12.0002.633 installed in C:Program Files (x86)Debugging Tools for Windows (x86)

VisualDDK Installation

Virtual Machine Installation

Installed DDK Launch Monitor with default settings in 32bit Windows XP Pro VM and rebooted.

It puts this in the boot.ini

Commuication with VM

I can ping the VM ip address from the host no problem

DDKLaunch Monitor does seem to get a connection of some sort

Bridged through my Wireless adapter through which I connect my host.

Issue attaching to Virual Machine Kernal

When I try the test I get this

>>>>>>>> TargetInfo::CleanSystemSymbols(0x0000000000000000,0x00720050005C003A)

Restarting kd transport

Opened \.pipekd_Windows_XP_Professional

Waiting to reconnect...

READ: Wait for type 7 packet

Resync packet id ...Kd sync initial break: on

800703E3,1,0) fails.

Throttle 0x10 write to 0x1

800703E3,1,0) fails.

Send sync break

Send Break in ...

800703E3,1,0) fails.

This just continues…

Other Notes

I can however, connect and debug the Kernel via VMMon64.exe or VMMon.exe from the VirtualKD environment supplied with VisualDDK as per the intructions from the “Windows Kernel Debugger booster for Virtual Machines” topic at http://virtualkd.sysprogs.org/

Can anyone help? im keen to get this going.

Cheers

[NeWbY]

At the screen where you can select which ‘os’ you want to load (before windows loads), you should start the debugging. You will see the window ‘Connecting to kernel debugging session…’ open with all fails calls. Then you should select the ‘Microsoft Windows XP Professional [VirtualKD]’ at the ‘os’ selection window so windows starts. This might take a while before windows start, but when windows is starting you should see the ‘Connecting to kernel debugging session…’ show different logs and it should start the kernel debugging session.
You can’t debug yet until windows has fully started and the DDKLaunch monitor has connected with the debugging session.

[Driver N00b]

Thanks for your response, Can i break down your suggestions just to make sure i understand?

At the screen where you can select which ‘os’ you want to load (before windows loads), you should start the debugging. I assume you mean the VM XP pro. Yes i am selecting the [VirtualKD] when i start the OS? Or do you mean i need to start debugging mode on my x64 Windows 7 host?

You will see the window ‘Connecting to kernel debugging session…’ open with all fails calls. I do not see this, where am i meant to be seeing this?

Then you should select the ‘Microsoft Windows XP Professional [VirtualKD]’ at the ‘os’ selection window so windows starts. Not sure, you have mentioned this above. I am debugging from a real x64 Windows 7 box trying to debug a virtual machine kernel. Maybe you assume i am going from VM to VM.

This might take a while before windows start, but when windows is starting you should see the ‘Connecting to kernel debugging session…’ show different logs and it should start the kernel debugging session.

You can’t debug yet until windows has fully started and the DDKLaunch monitor has connected with the debugging session.
I understand i need the DDK Launch Monitor to be running to install the driver interactively, but i cant even connect to the kernel from the VisualDDK launcher.

I have x64 Windows 7, Visual Studio 2008 with VisualDDK installed.
I have installed the DDKLaunchMonitor on the VM target and are just trying to follow the quick start guide, step by step to just get a basic connection to the targets kernel. But im not getting that far. I can however use the VMMon.exe using windows KD.EXE command line debugger to connect to the kernel. But this is not ideal.
Im sure if i can get that working, i can get the visual environment working also.

[Driver N00b]

SOLUTION
OK all working now.
Thanks to the previous New By as i think this was what you were trying to tell me although it was not obvious to me.

1. You must WAIT at the OS Boot menu.
2. Then you can start the VisualDDK launcher on the Visual Studio side.
3. Then you can select the Virtual Machine. (you cannot do this until the VM is running, but you cannot boot the VM completely. You must wait at the boot menu.
4. Then Launch the DDK Launcher from VS.
5. Then select the Boot menu item for kernel debugging.
6. You will get errors while the kernel debugger looks for the kernel connection but at some point it will connect.
7. Then you can debug the driver. Everything starts working.
After you have connected you can stop and start the debug sessions and start new projects without rebooting the VM each time.

Thanks

[Anonymous]

Hi,

I am facing a similar problem but my problem is with windbg.
I am running x86 win xp vmimage(target machine) on top of x64 win 7(host machine). I have modified the boot.ini of the target machine as following:

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS=”Microsoft Windows XP Professional” /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)WINDOWS=”Microsoft Windows XP Professional Debug” /noexecute=optin /fastdetect /debug /debugport=com1 /baudrate=115200

and using the following command line to run windbg and connect to target machine’s kernel:
cd C:WinDDK7600.16385.1Debuggers
windbg -b -k com:pipe,port=\.pipecom1,resets=0

I have also made the necessary changes to the serial port settings of the vm as shown in the following image:

[img]C:srlport.jpg[/img]

But despite doing all this I am unable to connect windbg of host machine to connect to the kernel of target machine. I always get the folowing output displayed on windbg:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.pipecom1
Waiting to reconnect…

This is troubling me since many days and i have reinstalled the winddk also to verify the installation. Any suggestion will be of great help.

Thanks,
Saurabh

[Anonymous]

This really helped me! Thank you

[Author]

Posts