windbg first connect then stuck on “Debuggee not connected.” message during kernel debugging

Question

I am trying to do Windows kernel debugging so I have set up two machines for this purpose:

1. HOST - DEBUGGER - The computer that runs the windbg debugger

Answer 1

You can try Bellavista.exe to create a new debug entry and look for the differences.

Answer 2

It looks like you got the debugger attached to the target. (1) Ignore WinDbg status message. The best way to see if you're connected to the target is to try a few commands. (2) When I debug a virtual machine, the serial port that I'm using also goes missing, but it looks like you figured that out (good job).

In order to issue commands you need to break into the kernel. Click "Debug->Break" and try the following commands:

.reload
!ustr srv!SrvComputerName 

That should give you the target system computer name.

If you want to learn more about kernel debugging, I would check out TheSourceLens on YouTube. As for literature, I can't recommend any books, because most information I find are online. However, I would recommend checking out OSR Online. Happy debugging.