From: Nicholas Amon <namon@xceedium.com>
To: kvm@vger.kernel.org
Subject: Unable to single-step in kvm, always results in a resume
Date: Tue, 19 Jan 2010 09:23:25 -0500 [thread overview]
Message-ID: <4B55C05D.6030408@xceedium.com> (raw)
Hi All,
I am trying to single-step through my kernel using qemu and kvm. I have
run qemu via:
qemu-system-x86_64 -s -S -hda /home/nickamon/lab1/obj/kernel.img and
also connected to the process using gdb.
Problem is that whenever I try and step instruction, it seems to resume
my kernel rather than allowing me to progress instruction by
instruction. I have built the kvm snapshot from git and still no luck.
Tried following the code for a few hours and have no luck. Any suggestions?
Thanks,
Nicholas
next reply other threads:[~2010-01-19 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 14:23 Nicholas Amon [this message]
2010-01-19 15:11 ` Unable to single-step in kvm, always results in a resume Jan Kiszka
2010-01-19 15:13 ` Jan Kiszka
[not found] ` <4B566CB5.7080804@xceedium.com>
2010-01-20 10:08 ` Jan Kiszka
2010-01-20 14:34 ` Nicholas Amon
2010-01-22 3:59 ` Nicholas Amon
2010-01-22 15:06 ` Jan Kiszka
2010-01-29 3:57 ` Nicholas Amon
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=4B55C05D.6030408@xceedium.com \
--to=namon@xceedium.com \
--cc=kvm@vger.kernel.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