From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Barry Silverman <barry-H+STxiiVszcAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Debugging KVM
Date: Tue, 27 Feb 2007 09:01:54 +0200 [thread overview]
Message-ID: <45E3D762.8030601@qumranet.com> (raw)
In-Reply-To: <loom.20070226T221352-244-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
Barry Silverman wrote:
> 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?
>
>
Various techniques are used depending on the bug and the weather. If a
guest won't boot, I dump a list of visited instruction pointers from
qemu and do a binary search on that using the kvm hardware breakpoint
feature. If the guest is Linux, you can modify it to check itself
mode. For mmu trouble, sometimes enabling AUDIT in mmu.c helps;
sometimes I have to add a test for a specific misbehaving address. For
host crashes, printks+netconsole are the way (though a kernel debugger
might help here; I'm just used to printks).
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-02-27 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 21:16 Debugging KVM Barry Silverman
[not found] ` <loom.20070226T221352-244-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-27 7:01 ` Avi Kivity [this message]
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=45E3D762.8030601@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=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