All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 207389] Regression in nested SVM from 5.7-rc1, starting L2 guest locks up L1
Date: Mon, 29 Jun 2020 06:17:11 +0000	[thread overview]
Message-ID: <bug-207389-28872-mkehiKh9rM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207389-28872@https.bugzilla.kernel.org/>

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

--- Comment #2 from Mitch (mitch@0bits.com) ---
Ok, just re-read this bug and i'm seeing slightly different behavior. My L2
locks up with the same message "BUG: soft lockup - CPU#x stuck for xxs". L1 and
L0 sees no errors at all.

If i move L0 to 5.6.19 then i see no lockups on L1 or L2. 

If i move L0 to 5.7.x (tested even latest 5.7.6) then L2 locks up with the same
message.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-06-29 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:23 [Bug 207389] New: Regression in nested SVM from 5.7-rc1, starting L2 guest locks up L1 bugzilla-daemon
2020-06-29  5:48 ` [Bug 207389] " bugzilla-daemon
2020-06-29  6:17 ` bugzilla-daemon [this message]
2020-06-30 13:53 ` 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=bug-207389-28872-mkehiKh9rM@https.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.