From: Barry Silverman <barry-H+STxiiVszcAvxtiuMwx3w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Debugging KVM
Date: Mon, 26 Feb 2007 21:16:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20070226T221352-244@post.gmane.org> (raw)
I am curious what techniques are being used to debug problems with KVM.
Are you using the qemu GDB stub to step the guest, or using KDB/KGDB to debug
the driver-level code, or just using a kernel printfs?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-02-26 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 21:16 Barry Silverman [this message]
[not found] ` <loom.20070226T221352-244-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-27 7:01 ` Debugging KVM Avi Kivity
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=loom.20070226T221352-244@post.gmane.org \
--to=barry-h+stxiivszcavxtiumwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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