public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "bugzilla-daemon@bugzilla.kernel.org"
	<bugzilla-daemon@bugzilla.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Bug 56971] New: [nested virt] L1 CPU Stuck when booting a L2 guest
Date: Sat, 27 Apr 2013 13:03:19 +0200	[thread overview]
Message-ID: <517BB077.4030300@web.de> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A10CA61D4@SHSMSX101.ccr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

On 2013-04-27 08:02, Ren, Yongjie wrote:
> CCed Jan Kiszka.
> I did some bisection and found the following commit introduced this bug.
> The bug still exists in the latest kvm.git next branch.
> 
> commit 5f3d5799974b89100268ba813cec8db7bd0693fb
> Author: Jan Kiszka <jan.kiszka@siemens.com>
> Date:   Sun Apr 14 12:12:46 2013 +0200
> 
>     KVM: nVMX: Rework event injection and recovery
> 
> 

I've reproduced some lock-up of L1 that starts to show with my commit.
Debugging...

Thanks for reporting,
Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-04-27 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 14:32 [Bug 56971] New: [nested virt] L1 CPU Stuck when booting a L2 guest bugzilla-daemon
2013-04-22 14:41 ` [Bug 56971] " bugzilla-daemon
2013-04-27  6:02 ` [Bug 56971] New: " Ren, Yongjie
2013-04-27 11:03   ` Jan Kiszka [this message]
2013-04-27  6:02 ` [Bug 56971] " bugzilla-daemon
2013-04-27 11:03 ` bugzilla-daemon
2013-05-29  7:45 ` bugzilla-daemon
2013-05-29  7:45 ` bugzilla-daemon
2013-05-29  7:46 ` bugzilla-daemon

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=517BB077.4030300@web.de \
    --to=jan.kiszka@web.de \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=yongjie.ren@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox