All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/2 (for 2.10)] docs: document support lifetime for features
Date: Mon, 24 Jul 2017 15:11:08 +0100	[thread overview]
Message-ID: <20170724141108.GA11443@redhat.com> (raw)
In-Reply-To: <ee0b3e06-7037-f2c9-18e9-1fb1dcb0784a@redhat.com>

On Mon, Jul 24, 2017 at 03:49:29PM +0200, Paolo Bonzini wrote:
> On 19/07/2017 13:56, Thomas Huth wrote:
> > +@node Machine types
> > +@section Machine types
> > +
> > +For architectures which aim to support live migration compatibility
> > +across releases, each release will introduce a new versioned machine
> > +type. For example, the 2.8.0 release introduced machine types
> > +``pc-i440fx-2.8'' and ``pc-q35-2.8'' for the x86_64/i686 architectures.
> > +
> > +To allow live migration of a guest running on a 2.8.0 release to a
> > +2.9.0, the QEMU 2.9.0 version must support the ``pc-i440fx-2.8'' and
> > +``pc-q35-2.8''. To allow users live migrating VMs to skip multiple
> > +intermediate releases when upgrading, new releases of QEMU will
> > +support machine types from many previous versions.
> > +
> > +The supported lifetime for versioned machine types is 12 releases,
> > +which is equivalent to 4 years worth of previous QEMU releases.
> 
> I think there's still no consensus on this.

Indeed, which is exactly why I sent this patch - we need to come up
with a sensible policy here, so we can stop repeating the same debate
over & over & over each time some proposes a patch to kill off some
random old machine type.

The 12 release / 4 year figure was a fairly arbitrary starting
point to which I'd be hoping to see critical reviewer feedback
on (with possible counterproposals) so we can try to get something
documented, to put an end to the repeated debates in this area
each time someone proposes a patch.

>                                              The first two paragraphs
> should be added to the documentation for -machine in qemu-options.hx,
> since "-machine [type=]foo" is currently not documented at all.

I'll happily send a patch for the docs for qemu-options.hx.

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 :|

  reply	other threads:[~2017-07-24 14:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:08 [Qemu-devel] [PATCH v5 0/2 (for 2.10] Document deprecated features & support lifecycle Daniel P. Berrange
2017-07-19 10:08 ` [Qemu-devel] [PATCH v5 1/2 (for 2.10)] docs: document support lifetime for features Daniel P. Berrange
2017-07-19 11:56   ` Thomas Huth
2017-07-24 13:49     ` Paolo Bonzini
2017-07-24 14:11       ` Daniel P. Berrange [this message]
2017-07-24 14:26         ` Paolo Bonzini
2017-07-24 14:47           ` Daniel P. Berrange
2017-07-24 14:58             ` Paolo Bonzini
2017-07-19 10:08 ` [Qemu-devel] [PATCH v5 2/2 (for 2.10)] docs: document deprecated features in appendix Daniel P. Berrange
2017-07-19 11:51   ` Thomas Huth
2017-07-25  9:35   ` Thomas Huth
2017-07-25 11:21     ` Daniel P. Berrange
2017-07-24 13:45 ` [Qemu-devel] [PATCH v5 0/2 (for 2.10] Document deprecated features & support lifecycle Stefan Hajnoczi

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=20170724141108.GA11443@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /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.