qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "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: Tue, 20 Nov 2018 13:14:29 +0100	[thread overview]
Message-ID: <20c9d320-f189-f65a-8a29-ddead8949d45@redhat.com> (raw)
In-Reply-To: <20181120114422.GA5072@work-vm>

On 20/11/18 12:44, 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.

Yes, of course.

Paolo

  reply	other threads:[~2018-11-20 12:14 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 [this message]
2019-04-10 18:26   ` Cole Robinson
2019-04-10 18:26     ` Cole Robinson
2019-04-12  7:47     ` Paolo Bonzini
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=20c9d320-f189-f65a-8a29-ddead8949d45@redhat.com \
    --to=pbonzini@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).