qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	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 16:50:54 +0000	[thread overview]
Message-ID: <20181112165053.GF2293@work-vm> (raw)
In-Reply-To: <20181112161829.GU3602@redhat.com>

* Daniel P. Berrangé (berrange@redhat.com) wrote:
> On Sun, Nov 04, 2018 at 11:19:57PM +0100, Paolo Bonzini wrote:
> > On 02/11/2018 17:54, Daniel P. Berrangé wrote:
> > > We have usually followed a rule that new machine types must not
> > > affect runability of a VM on a host. IOW new machine types should
> > > not introduce dependancies on specific kernels, or hardware features
> > > such as CPU flags.
> > 
> > > Anything that requires a new kernel feature thus ought to be an
> > > opt-in config tunable on the CLI, separate from machine type
> > > choice.
> > 
> > Unless someone tinkered with the module parameters, they could not even
> > use nested virtualization before 4.20.  So for everyone else, "-cpu
> > ...,+vmx" does count as an "opt-in config tunable on the CLI" that
> > requires 4.20.
> >
> > For those that did tinker with module parameters, we can grandfather in
> > the old machine types, so that they can use nested virtualization with
> > no live migration support.  For those that did not, however, I don't
> > think it makes sense to say "oh by the way I really want to be able to
> > migrate this VM" on the command line, or even worse on the monitor.
> 
> IIUC, 4.20 is only required from POV of migration state. Is it thus
> possible to just register a migration blocker if QEMU is launched
> on a host with kernel < 4.20.
> 
> 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.

Dave

> Regards,
> Daniel
> -- 
> |: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-            https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2018-11-12 16:51 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 [this message]
2018-11-12 16:53                                     ` Paolo Bonzini
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=20181112165053.GF2293@work-vm \
    --to=dgilbert@redhat.com \
    --cc=berrange@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=pbonzini@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).