Hi, I hope you can help a newbie getting started with VirtualDDK.

I have two targets, a virtual Win7-32 in VMware and a physical Win7-32 with a nullmodem cable. VirtualBox is not stable with the kind of driver I wish to install.

The physical machine won’t boot with the [VirtualKD] [debugger enabled] option. But with normal boot, discovery request does show up in DDKLaunchMonitor. But the window named Connecting to kernel debugging session keeps saying “10 write to 0x1” without continuing.

On the VM things are rougher. Normal boot does not get discovery requests. [VirtualKD] boot gets discovery requests. But now Connecting to… says “Throttle 0x10 write to 0x1 n 8007803E1,1,0) fails.”

When I cancel the connection attempt to the physical machine it does not have consequenses. But when I cancle the attempt to the VM I get the message “The named pipe used for debugging is busy. If you have WinDbg open, please close it!”. This happens in spite of me not having selected a named pipe as the connection message, but rather a discovered VM.

The very first attempt with the VM did get me further, but no actual debuggint took place. Instead, certain drivers were put on the slow startup list. Now I can’t get back to that state. In the meantime I have rebooted all targets and the host multiple times.

Any help appreciated!

Thanks,
Borge