- This topic has 5 replies, 2 voices, and was last updated 12 years, 11 months ago by
.
-
Posts
-
Hello,
If I use the “Restore VM snapshot” option then I can no longer connect the debugger. WinDbg stops at “Waiting to reconnect…”
My snapshot is of a running VM which has been booted using the VirtualKD boot entry before taking the snapshot. The only solution is to restart the VM and connect at boot.
Do you have any idea why it doesn’t work?
P.S. I wanted to debug the problem by looking at the source code of VirtualKD that I see is mentioned on the website, but not available for download. The sourceforge SVN repository appears to be empty. Where can I download it from?
One more detail:
If I close WinDbg and try “Run debugger”, I get a
“Could not start kernel debugging using com:pipe,resets=0,reconnect,port=\.pipekd_xp-sp3-x86-test parameters, Win32 error 0n231
All pipe instances are busy.”
i have no idea. tested, encountered the same. probably,- because you should attach during boot selection as when debugging with VisualDDK project
@sn0w wrote:
because you should attach during boot selection as when debugging with VisualDDK project
That won’t work for me. I use snapshots in order to make the debugging faster:
– avoid losing time waiting to Windows to boot
– go to a point in time where all the conditions for reproducing a bug are metWinDbg without VirtualKD has no problem connecting to a restored snapshot. It is only with VirtualKD that it doesn’t work.
- You must be logged in to reply to this topic.