Windbg 未连接到目标电脑
我不知道我哪里出错了。我尝试将 mi 主机电脑（Windows 7）连接到目标电脑（带有 Windows 7 的虚拟机），以便开始远程内核调试。
Vmware（虚拟机）串口设置：
Windgb 内核调试：
启动虚拟机设置：
如果我打开或关闭虚拟机，什么也不会发生..
有谁知道我做错了什么？顺便问一下，是否可以使用 LiveKd 查看驱动程序中的变量内容？
I don't know where i make a mistake. I try to connect mi host pc (Windows 7) to target pc (virtual machine with Windows 7) in order to start with remote kernel debugging.
Vmware (virtual machine) serial port settings:
Windgb kernel debugging:
Boot virtual machine settings:
If I turn on or turn off virtual machine, nothing happens..
Does anyone know what I'm doing wrong? By the way, is it possible to view content of variables in a driver using LiveKd?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我将调试端口更改为 2，主机可以连接到目标计算机，但 Windbg 收到错误消息“断言失败：缺少 StreamContext 支持...”并且 VM 挂在“正在启动 Windows”处，并且没有任何反应。
I changed debug port to 2 and host machine can connect to target machine, but windbg get error message "Assertion failed: Missing StreamContext Support ..." and VM hangs at the "Starting Windows" and nothing more happens..
这些设置对我来说看起来是正确的。有时，当我看到相同的行为时，我只是告诉 WinDbg“中断”，这似乎就完成了连接。
Those settings look correct to me. Occasionally when I see the same behavior I just tell WinDbg to "Break" and that appears to finish the connection.
我一直在为同样的事情而苦苦挣扎。我已经有一段时间没有花大量时间使用 Windbg 进行内核调试了。我几乎所有事情都运行 Linux，所以这次我尝试使用两个由 Libvirt 管理的 KVM/QEMU VM。那里有很多不同的复杂性，因为我使用的 Libvirt 版本不提供在虚拟机之间连接串行端口的简单“ui”方法（Libvirt 提示：串行端口的 XML 设置，一个系统的串行端口源类型必须设置为“bind”，并且一个系统设置为“connect”，即使对于串行类型“unix”）
终于，我能够使用在两个虚拟机上使用 Putty 并来回聊天，确认我选择的 COM 端口确实已连接。
...我的调试主机上的 Windbg 仍然继续说“正在等待连接...”
只是确认 @jcopenha 的答案，发送 Break 对我来说确实有效（我我的笔记本电脑 kbd 上没有 Break，所以我使用
调试菜单来选择“Break”）。目标系统被冻结（是的，在目标完全启动之后，这是另一个我不记得答案的问题），并且
!process为我提供了来自目标系统的有趣信息。我会对他们的答案投赞成票，但我是 StackOverflow 的新手，还没有声誉。谢谢你！
I've been struggling with much the same thing. It's been a while since I've spent much time kernel debugging with Windbg. I run Linux for pretty much everything, so this time I tried using two KVM/QEMU VM's managed by Libvirt. Lots of different complexity there, since the version of Libvirt I'm using doesn't provide easy "ui" methods of connecting serial ports between VMs (Libvirt hint: the XML setup for the serial ports, one system's Serial port source type must be set to "bind" and one system set to "connect", even for serial type "unix")
Finally, I was able to use Putty on both VM's and chat back and forth, confirming the COM ports I've chosen are indeed connected.
... and still Windbg on my debug host continued to say "Waiting to connect..."
Just confirming @jcopenha's answer, sending Break did just work for me (I don't have Break on my laptop kbd, so I used the
Debug Menuto choose "Break").The Target system is frozen (yes, after the target was fully booted, which was another question I couldn't remember the answer to), and
!processgives me interesting info from the target system. I would Up-Vote their answer, but I am new to StackOverflow and don't have the reputation yet.Thank you!