From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Mark Mielke <mark.mielke@gmail.com>
Cc: 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 11:11:01 +0100 [thread overview]
Message-ID: <8f0f7339-5f47-46d0-20a9-343badad4d0f@redhat.com> (raw)
In-Reply-To: <20190118100159.GA2483@work-vm>
On 18/01/19 11:02, Dr. David Alan Gilbert wrote:
>>
>> It fails if the flag is set, rather than if any nested virtualization has
>> been used before.
>>
>> I'm concerned I will end up with a requirement for *all* guests to be
>> restarted in order to migrate them to the new hosts, rather than just the
>> ones that would have a problem.
> I think you should be able to migrate from 2.12->3.1 like this, but
> you'd hit the problem when you then try and migrate again between your
> new QEMUs.
>
> I guess we could modify it to wire it to machine type, so that
> older machine types didn't block.
That would also be wrong. The old machine types _could_ be using KVM
and they have no way to block the live migration.
The solution is to restart the VM using "-cpu host,-vmx".
Paolo
next prev parent reply other threads:[~2019-01-18 10:11 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 [this message]
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
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=8f0f7339-5f47-46d0-20a9-343badad4d0f@redhat.com \
--to=pbonzini@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 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.