From: Jan Kiszka <jan.kiszka@web.de>
To: Hu Yaohui <loki2441@gmail.com>
Cc: qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Fwd: Guest VM debug (Int 3 panic)
Date: Thu, 26 Sep 2013 21:07:02 +0200 [thread overview]
Message-ID: <524485D6.2050205@web.de> (raw)
In-Reply-To: <CAHqbYQvcN_A06u_vCotmkwGuYr4jNGk6jXcdLpA0UASmBMCriw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On 2013-09-26 20:53, Hu Yaohui wrote:
> Hi Jan,
> I am working on some Nested VM related projects. Some other teammates have
> made the modifications to the kvm module.
And these modifications cannot cause the misguided INT3?
> Most of my work depends on his.
> If I could not use Qemu Debug method. Could you please suggest some other
> debugging methods to debug the L2 guest OS(printk, hijack kernel function,
> or something else)?
Remove L0 while debugging L2 and, once it works, move L1/L2 back over
L0? Your setup seems to be pretty special with (for us) unknown
requirements, so it's hard to suggest what to do best.
In any case, you seem to be pretty much "off-track" and may either have
to stabilize the whole stack on your own, possibly back-porting
essential nVMX fixes from latest versions, or rebase & share your
changes so that we can help again.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-09-26 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 17:55 [Qemu-devel] Guest VM debug (Int 3 panic) Hu Yaohui
2013-09-25 18:08 ` [Qemu-devel] Fwd: " Hu Yaohui
2013-09-26 6:08 ` Jan Kiszka
2013-09-26 14:14 ` Hu Yaohui
2013-09-26 17:26 ` Jan Kiszka
2013-09-26 18:53 ` Hu Yaohui
2013-09-26 19:07 ` Jan Kiszka [this message]
2013-09-26 19:20 ` Hu Yaohui
2013-09-26 21:51 ` Hu Yaohui
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=524485D6.2050205@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=loki2441@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).