public inbox for kvm@vger.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: Tue, 30 Jun 2020 13:53:11 +0000	[thread overview]
Message-ID: <bug-207389-28872-aOhmyeGFTI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207389-28872@https.bugzilla.kernel.org/>

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

Maxim Levitsky (maximlevitsky@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |maximlevitsky@gmail.com

--- Comment #3 from Maxim Levitsky (maximlevitsky@gmail.com) ---
5.7 kernel has several nested virtualization issues that mostly make it
useless, but good news are that all of this was fixed, and 5.8 kernel should
contain all the fixes.

On my machine I am able even to run even windows 10 nested (mostly for fun,
don't need it), I can play (a bit slow but works) some linux games in nested
VM, with virtio-gpu on top of virtio-gpu, and I was even able to run a win98 VM
nested on KVM, and it works as good as it works non nested (has bunch of issues
that probably will never get fixed sadly).

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

      parent reply	other threads:[~2020-06-30 13:53 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
2020-06-30 13:53 ` bugzilla-daemon [this message]

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-aOhmyeGFTI@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox