From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Liran Alon <liran.alon@oracle.com>,
jmattson@google.com, ehabkost@redhat.com, kvm@vger.kernel.org,
mtosatti@redhat.com, qemu-devel@nongnu.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [QEMU PATCH v2 0/2]: KVM: i386: Add support for save and restore nested state
Date: Mon, 12 Nov 2018 17:53:38 +0100 [thread overview]
Message-ID: <81d4f6c0-ede1-8986-8d7f-1741fc6de18a@redhat.com> (raw)
In-Reply-To: <20181112165053.GF2293@work-vm>
On 12/11/2018 17:50, Dr. David Alan Gilbert wrote:
>> Migration has always been busted historically, so those people using
>> nested VMX already won't be hurt by not having ability to live migrate
>> their VM, but could otherwise continue using them without being forced
>> to upgrade their kernel to fix a feature they're not even using.
> Yes, although I am a bit worried we might have a population of users
> that:
> a) Have enabled nesting
> b) Run VMs with vmx enabled
> c) Don't normally actually run nested guests
> d) Currently happily migrate.
Hmm, let's add a migration blocker for nested virtualization.
Paolo
next prev parent reply other threads:[~2018-11-12 16:53 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 12:46 [Qemu-devel] [QEMU PATCH v2 0/2]: KVM: i386: Add support for save and restore nested state Liran Alon
2018-09-16 12:46 ` [Qemu-devel] [QEMU PATCH v2 1/2] i386: Compile CPUX86State xsave_buf only when support KVM or HVF Liran Alon
2018-09-16 12:46 ` [Qemu-devel] [QEMU PATCH v2 2/2] KVM: i386: Add support for save and restore nested state Liran Alon
2018-10-08 17:21 ` [Qemu-devel] [QEMU PATCH v2 0/2]: " Liran Alon
2018-10-15 18:10 ` Liran Alon
2018-10-31 1:03 ` Liran Alon
2018-10-31 18:17 ` Eduardo Habkost
2018-10-31 18:19 ` Paolo Bonzini
2018-10-31 18:50 ` Liran Alon
2018-10-31 18:59 ` Dr. David Alan Gilbert
2018-10-31 23:17 ` Liran Alon
2018-11-01 13:10 ` Dr. David Alan Gilbert
2018-11-01 15:23 ` Liran Alon
2018-11-01 15:56 ` Dr. David Alan Gilbert
2018-11-01 16:45 ` Jim Mattson
2018-11-02 3:46 ` Liran Alon
2018-11-02 9:40 ` Paolo Bonzini
2018-11-02 12:35 ` Dr. David Alan Gilbert
2018-11-02 12:40 ` Daniel P. Berrangé
2018-11-04 22:12 ` Paolo Bonzini
2018-11-02 12:59 ` Liran Alon
2018-11-02 16:44 ` Jim Mattson
2018-11-02 16:58 ` Daniel P. Berrangé
2018-11-02 17:01 ` Jim Mattson
2018-11-02 16:54 ` Daniel P. Berrangé
2018-11-02 16:58 ` Dr. David Alan Gilbert
2018-11-04 22:19 ` Paolo Bonzini
2018-11-12 16:18 ` Daniel P. Berrangé
2018-11-12 16:50 ` Dr. David Alan Gilbert
2018-11-12 16:53 ` Paolo Bonzini [this message]
2018-11-12 16:54 ` Daniel P. Berrangé
2018-11-13 0:00 ` Liran Alon
2018-11-13 0:07 ` Jim Mattson
2018-11-13 0:09 ` Liran Alon
2018-11-12 23:58 ` Liran Alon
2018-11-02 16:39 ` Jim Mattson
2018-11-03 2:02 ` Liran Alon
2018-11-08 0:13 ` Liran Alon
2018-11-08 0:45 ` Jim Mattson
2018-11-08 9:50 ` Paolo Bonzini
2018-11-08 9:57 ` Liran Alon
2018-11-08 17:02 ` Paolo Bonzini
2018-11-08 18:41 ` Liran Alon
2018-11-08 20:34 ` Paolo Bonzini
2018-11-12 14:51 ` Dr. David Alan Gilbert
2018-11-01 19:03 ` Liran Alon
2018-11-01 19:07 ` Dr. David Alan Gilbert
2018-11-01 19:41 ` Jim Mattson
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=81d4f6c0-ede1-8986-8d7f-1741fc6de18a@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).