From: Justin Cinkelj <justin.cinkelj@xlab.si>
To: elfutils-devel@sourceware.org
Subject: get backtrace of KVM VM from host
Date: Mon, 21 May 2018 08:27:00 -0000 [thread overview]
Message-ID: <9c68635a-3eac-cee5-d05f-dfc80bdaea2a@xlab.si> (raw)
(crossposting from KVM maillist)
Hi
Is it possible to get stack backtrace into KVM VM from the host side? So
if I run './stack -p PID' (stack from elfutilfs
https://sourceware.org/elfutils/), I get backtrace of some process. I
would like to do the same for VM. I can assume VM will run only a kernel
(a unikernel, like OSv or IncludeOS), so most/all debug symbols will be
there in a single file, and at least IncludeOS doesnt load any code
beside its own kernel.
I did notice KVM_GET_REGS and KVM_SET_MEMORY_REGION, and at least for
trivial examples (like https://github.com/dpw/kvm-hello-world) this
provides enough information to track which code was loaded into VM,
observe current stack content and registers. I can only guess much more
work is required to get similar result with qemu-kvm. Hence I'm asking
if this is already implemented.
Thank you,
Justin
next reply other threads:[~2018-05-21 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 8:27 Justin Cinkelj [this message]
2018-05-22 14:05 ` Mark Wielaard
2018-05-22 15:07 ` Justin Cinkelj
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=9c68635a-3eac-cee5-d05f-dfc80bdaea2a@xlab.si \
--to=justin.cinkelj@xlab.si \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).