From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-options: document existance of versioned machine types
Date: Wed, 26 Jul 2017 09:07:54 +0100 [thread overview]
Message-ID: <20170726080754.GB28914@redhat.com> (raw)
In-Reply-To: <be2523ce-7505-b3dd-d359-e91ac25f3cc4@redhat.com>
On Tue, Jul 25, 2017 at 01:46:23PM -0400, John Snow wrote:
>
>
> On 07/25/2017 10:10 AM, Daniel P. Berrange wrote:
> > The -machine docs did not explain what the versioned machine
> > types are for, nor that they'll be maintained across
> > releases.
> >
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> > qemu-options.hx | 15 ++++++++++++++-
> > 1 file changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/qemu-options.hx b/qemu-options.hx
> > index 746b5fa75d..9f6e2adfff 100644
> > --- a/qemu-options.hx
> > +++ b/qemu-options.hx
> > @@ -49,7 +49,20 @@ STEXI
> > @item -machine [type=]@var{name}[,prop=@var{value}[,...]]
> > @findex -machine
> > Select the emulated machine by @var{name}. Use @code{-machine help} to list
> > -available machines. Supported machine properties are:
> > +available machines.
> > +
> > +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 guests from QEMU version 2.8.0, to QEMU
> > +version 2.9.0, the 2.9.0 version must support the ``pc-i440fx-2.8''
> > +and ``pc-q35-2.8'' machines too. 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.
> > +
> > +Supported machine properties are:
> > @table @option
> > @item accel=@var{accels1}[:@var{accels2}[:...]]
> > This is used to enable an accelerator. Depending on the target architecture,
> >
>
> Seems like an improvement to me, but do we have any formal policy on how
> long we support said machine types? The new wording prompts that question.
I wasn't going to mention that in this patch, to avoid delay on getting it
merged. I was going to send a further patch that makes it explicit that we
will never delete machine types for as long as any active QEMU contributor
has need for them in downstream version they maintain
> Reviewed-by: John Snow <jsnow@redhat.com>
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 :|
next prev parent reply other threads:[~2017-07-26 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 14:10 [Qemu-devel] [PATCH] qemu-options: document existance of versioned machine types Daniel P. Berrange
2017-07-25 17:46 ` John Snow
2017-07-25 17:49 ` Paolo Bonzini
2017-07-26 8:07 ` Daniel P. Berrange [this message]
2017-07-26 18:50 ` John Snow
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=20170726080754.GB28914@redhat.com \
--to=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@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 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.