From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 53851] nVMX: Support live migration of whole L1 guest
Date: Wed, 09 Jun 2021 09:15:04 +0000 [thread overview]
Message-ID: <bug-53851-28872-Vdw8UMGk97@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-53851-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=53851
--- Comment #3 from mlevitsk@redhat.com ---
On Wed, 2021-06-09 at 08:55 +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=53851
>
> --- Comment #2 from christian.rohmann@frittentheke.de ---
> Sorry for replying to this rather old bug - I was pointed to this via
> https://www.linux-kvm.org/page/Nested_Guests#Limitations
>
>
> If I may ask, is this really the last state of discussion and work on this
> issue?
> Looking at i.e.
>
> *
> https://github.com/qemu/qemu/commit/ebbfef2f34cfc749c045a4569dedb4f748ec024a
> *
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=039aeb9deb9291f3b19c375a8bc6fa7f768996cc
>
>
> there have been commits for the kernel as well as QEMU to support migration
> of
> nested VMs.
>
AFAIK, running nested guests and migration while nested guest is running should
work on both Intel and AMD, but there were lots of fixes in this area recently
so a very new kernel should be used.
Plus in some cases if the nested guest is 32 bit, the migration still can fail,
on Intel at least, last time I checked. On AMD I just recently fixed
such issue for 32 bit guest and it seems to work for me.
I also know that if the nested guest is hyper-v enabled (which is a bit
overkill as
this brings us to a double nesting), then it crashes once in a whileafter lots
of migration
cycles.
So there are still bugs, but overall it works.
Best regards,
Maxim Levitsky
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2021-06-09 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 14:36 [Bug 53851] New: nVMX: Support live migration of whole L1 guest bugzilla-daemon
2013-02-14 14:37 ` [Bug 53851] " bugzilla-daemon
2013-02-26 15:27 ` bugzilla-daemon
2015-03-17 3:53 ` bugzilla-daemon
2018-02-15 9:44 ` bugzilla-daemon
2021-06-09 8:55 ` bugzilla-daemon
2021-06-09 9:14 ` Maxim Levitsky
2021-06-09 9:15 ` 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-53851-28872-Vdw8UMGk97@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.