From: Pantelis Koukousoulas <pktoss@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] windbg and serial
Date: Thu, 23 Apr 2009 15:32:39 +0300 [thread overview]
Message-ID: <1295ed070904230532u7ff434f9r4516a00178d40823@mail.gmail.com> (raw)
Hi,
I 've been trying to get windbg in one guest to debug a kernel in another guest
through an emulated serial port connection. There are several blog posts and
a few mails to this list and kvm/kvm-devel from people who claim to have made
this functionality to work, yet nothing seems to work for me with
latest qemu git.
What I 've tried:
Start the debuggee guest with -serial tcp:localhost:1234,server
Start the debugger guest with -serial tcp:localhost:1234
(The debuggee has the right options (/debugport, /baudrate) in its boot.ini.)
When the debuggee starts and after the connection of the sockets is done,
both guests start to boot and the debuggee stops in its boot menu. I
'm selecting
the "debug" menu option (to stop the countdown timer).
Then I wait until the debugger boots fully, start windbg, ask it to connect via
com1, baudrate=112500bps and when it says
"waiting to reconnect..." I 'm continuing the debuggee boot process.
At this point I would expect to see something like "Debugger
connection established'
in the debugger guest, yet nothing. It just continues waiting and
after a while windbg
just closes with an "unable to connect" message. At this point the
debuggee continues
boot normally.
I 've verified that the serial connection works by trying
hyperterminal on both guests
and observing each to be able to send/receive text to the other just fine.
The qemu versions tested were current git as of today and also with the patch in
http://damogran.de/blog/archives/14-WinDbg-and-QEMU.html
The guests are both winxp sp3 32-bit. The host is 64-bit (kernel/userland) but
hopefully this is not very relevant for qemu.
Has anyone else here managed to make this configuration
(guest XP debugging another guest XP through serial port) work?
I 'd be interested in any ideas on how to achieve that or debug the
problem further.
Thanks in advance,
Pantelis
reply other threads:[~2009-04-23 12:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295ed070904230532u7ff434f9r4516a00178d40823@mail.gmail.com \
--to=pktoss@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).