From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Mielke <mark.mielke@gmail.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel@nongnu.org, christian.ehrhardt@canonical.com
Subject: Re: [Qemu-devel] Live migration from Qemu 2.12 hosts to Qemu 3.2 hosts, with VMX flag enabled in the guest?
Date: Fri, 18 Jan 2019 16:25:27 +0100 [thread overview]
Message-ID: <19ec0017-bd05-a847-b211-ebbdb141ebf6@redhat.com> (raw)
In-Reply-To: <CALm7yL0nFGC1hYfvASrOL2FzO88oZURiLs-a6pR7Cjp3XS0U_g@mail.gmail.com>
On 18/01/19 14:41, Mark Mielke wrote:
> It is useful to understand the risk. However, this is the same risk we
> have been successfully living with for several years now, and it seems
> abrupt to declare 3.1 and 3.2 as the Qemu version beyond which migration
> requires a whole cluster restart whether or not a L2 guest had been, or
> will ever be started on any of the guests.
Only if nested was enabled for the kvm_intel module. If you didn't
enable it, you didn't see any change with 3.1.
Nested was enabled for kvm_amd years ago. It was a mistake, but that's
why we didn't add such a blocker for AMD.
Paolo
next prev parent reply other threads:[~2019-01-18 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 5:32 [Qemu-devel] Live migration from Qemu 2.12 hosts to Qemu 3.2 hosts, with VMX flag enabled in the guest? Mark Mielke
2019-01-18 6:18 ` Christian Ehrhardt
2019-01-22 7:20 ` Like Xu
2019-01-18 10:02 ` Dr. David Alan Gilbert
2019-01-18 10:11 ` Paolo Bonzini
2019-01-18 10:16 ` Dr. David Alan Gilbert
2019-01-18 10:21 ` Daniel P. Berrangé
2019-01-18 12:57 ` Paolo Bonzini
2019-01-18 13:41 ` Mark Mielke
2019-01-18 15:25 ` Paolo Bonzini [this message]
2019-01-18 19:31 ` Dr. David Alan Gilbert
2019-01-22 22:58 ` Mark Mielke
2019-01-18 13:44 ` Daniel P. Berrangé
2019-01-18 14:09 ` Mark Mielke
2019-01-18 14:48 ` Daniel P. Berrangé
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=19ec0017-bd05-a847-b211-ebbdb141ebf6@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dgilbert@redhat.com \
--cc=mark.mielke@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).