- This topic has 0 replies, 1 voice, and was last updated 14 years, 4 months ago by
.
-
Posts
-
Hi IM using WinDBG over VirtualKD with VMWare.
In the past I used to use windbg over com (pipe) to debug guest running inside VMWare. I usually start the guest with the boot option that enables kernel debugging over serial (via pipe) but will not start windbg. The guest system would make attempt to connect to the debugger but it would eventually fail after a while (10-15 seconds) since there is not debugger running. Once the guest is up, I will start WinDBG and refresh. This would allow me to connect the debugger later on when my driver running inside the guest breaks or asserts.
Now with the VirtualKD I am unable to do this. If the guest is debug enabled and if there is no debugger running, the guest wouldn’t boot. It simply sits at they very beginning. Is there a way to fix this? I wonder whats going on?
Thanks,
Senthil
- You must be logged in to reply to this topic.