From: Paolo Bonzini <pbonzini@redhat.com>
To: Cole Robinson <crobinso@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] target/i386: kvm: add VMX migration blocker
Date: Fri, 12 Apr 2019 09:47:55 +0200 [thread overview]
Message-ID: <c348ffd5-a044-bc12-d1a7-50b7ab543045@redhat.com> (raw)
In-Reply-To: <f6c43c98-1319-85bb-c379-72d8caacf68d@redhat.com>
On 10/04/19 20:26, Cole Robinson wrote:
> On 11/20/18 6:44 AM, Dr. David Alan Gilbert wrote:
>> * Paolo Bonzini (pbonzini@redhat.com) wrote:
>>> Nested VMX does not support live migration yet. Add a blocker
>>> until that is worked out.
>>>
>>> Nested SVM only does not support it, but unfortunately it is
>>> enabled by default for -cpu host so we cannot really disable it.
>>>
>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>
>> So I'm OK with this, but it does need a release note warning whenever it
>> goes in, because it'll surprise those who've already enabled nesting
>> but don't use it on all their VMs.
>>
>
> We are hitting this in Fedora 30. Now that nested VMX is enabled by
> default at the kernel level, and virt-manager/boxes will use the
> equivalent of -cpu host by default, libvirt managedsave (migrate to
> file) and virt-manager snapshots (savevm) are rejected for default
> created VMs on intel. That's quite unfortunate.
>
> Any ideas on how to resolve this?
I think the simplest solution is just to finish implementation of nested
VMX live migration and backport it to Fedora 30.
Paolo
next prev parent reply other threads:[~2019-04-12 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 18:23 [Qemu-devel] [PATCH v2] target/i386: kvm: add VMX migration blocker Paolo Bonzini
2018-11-20 11:44 ` Dr. David Alan Gilbert
2018-11-20 12:14 ` Paolo Bonzini
2019-04-10 18:26 ` Cole Robinson
2019-04-10 18:26 ` Cole Robinson
2019-04-12 7:47 ` Paolo Bonzini [this message]
2019-04-12 7:47 ` Paolo Bonzini
2019-04-12 18:33 ` Cole Robinson
2019-04-12 18:33 ` Cole Robinson
2019-04-13 8:26 ` [Qemu-devel] R: " Paolo Bonzini
2019-04-13 8:26 ` Paolo Bonzini
2019-04-15 11:22 ` Dr. David Alan Gilbert
2019-04-15 11:22 ` Dr. David Alan Gilbert
2019-04-15 11:26 ` Paolo Bonzini
2019-04-15 11:26 ` Paolo Bonzini
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=c348ffd5-a044-bc12-d1a7-50b7ab543045@redhat.com \
--to=pbonzini@redhat.com \
--cc=crobinso@redhat.com \
--cc=dgilbert@redhat.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).