Hi, I've been pulling my hair out over this... I'm trying to establish a windows kernel debugging session by getting my windbg client to connect to my debugging target. Currently using Parallels Build 5584, with two Windows XP Pro guests communicating over virtual serial ports. One is set to boot with with debugging mode enabled and has its serial port configured to "server", while the other will be running the debugger itself and is set to "client". I've already confirmed communication between the two guests via hyperterminal and portmon.exe. The weird part is that at one point, when the stars were properly aligned, I was able to connect the debugger to the target, however I cannot get it to do it again and am now at a loss as to what's going on. There's only one other related thread on the forums regarding setting up this kind of debugging environment and unfortunately it is not working for me: http://forum.parallels.com/showthread.php?t=3439 I really would like see better documentation concerning ports and named pipes within the virtual machines... VMWare has been doing this for years and I may just have to go back if I can't get this to work.
Hello _Kylito_ I have asked our developers - debugger has not been tested yet with the build 5584. It used to work in previous builds. You can try the following as a workaround: press Break key in WinDbg when establishing the connection. Best regards, Xenos
