All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 56971] [nested virt] L1 CPU Stuck when booting a L2 guest
Date: Sat, 27 Apr 2013 11:03:27 +0000 (UTC)	[thread overview]
Message-ID: <20130427110327.6D4B711FACF@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-56971-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=56971





--- Comment #2 from Jan Kiszka <jan.kiszka@web.de>  2013-04-27 11:03:27 ---
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

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent 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
2013-04-27  6:02 ` [Bug 56971] " bugzilla-daemon
2013-04-27 11:03 ` bugzilla-daemon [this message]
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=20130427110327.6D4B711FACF@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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 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.