All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Neo Jia <neojia@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: how to debug unhandled vm exit: 0x11?
Date: Mon, 26 Jul 2010 19:14:39 +0300	[thread overview]
Message-ID: <4C4DB46F.3070509@redhat.com> (raw)
In-Reply-To: <AANLkTimN_zgCCm7_QRZLmHCuBdOGbnaHe_MpToZVvH4W@mail.gmail.com>

  On 07/26/2010 07:01 PM, Neo Jia wrote:
> hi,
>
> I am seeing an unhandled vm exit: 0x11 on Win7 with KVM-88 release and
> wondering if I am still able to dump the code from guest OS when this
> happens. But it looks that all instructions are 0s after adding one
> more print code after dumping the guest registers.
>
> And it is very likely that this problem is fixed in the latest qemu
> code base but I still would like to know how to debug and investigate
> this kind of problem. BTW, I am using 32-bit qemu + 64-bit KVM kernel
> module.
>
> unhandled vm exit: 0x11

The first step is to look up exit reason 0x11 in the manual and see what 
it means.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-07-26 16:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 16:01 how to debug unhandled vm exit: 0x11? Neo Jia
2010-07-26 16:14 ` Avi Kivity [this message]
2010-07-26 17:58   ` ewheeler
2010-07-27 10:04     ` Avi Kivity
2010-09-28 18:40       ` Neo Jia
2010-09-28 18:46         ` Neo Jia
2010-09-29  8:38         ` Avi Kivity
2010-10-01  6:16           ` Neo Jia
2010-10-01 14:29             ` Avi Kivity
2010-10-11  5:46               ` Neo Jia
2010-10-11  6:30                 ` Avi Kivity
2010-10-11  6:49                   ` Neo Jia
2010-10-11 14:27                     ` Avi Kivity
2010-10-11 14:31                       ` Avi Kivity
2010-10-11 15:00                         ` Avi Kivity
2010-10-12  4:09                       ` Neo Jia

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=4C4DB46F.3070509@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=neojia@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.