qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>,
	Marcel Apfelbaum <marcel.a@redhat.com>,
	qemu-devel@nongnu.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] q35: Remove old machine versions
Date: Tue, 25 Aug 2015 17:21:16 +0100	[thread overview]
Message-ID: <20150825162116.GD25920@redhat.com> (raw)
In-Reply-To: <87vbc5qadz.fsf@blackfin.pond.sub.org>

On Mon, Aug 24, 2015 at 11:54:48AM +0200, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
> 
> > On 08/19/2015 02:55 AM, Dr. David Alan Gilbert wrote:
> >> * Eduardo Habkost (ehabkost@redhat.com) wrote:
> >>> Migration with q35 was not possible before commit
> >>> 04329029a8c539eb5f75dcb6d8b016f0c53a031a, because q35 unconditionally creates
> >>> an ich9-ahci device, that was marked as unmigratable. So all q35 machines
> >>> before pc-q35-2.4 were unmigratable, and there's no point in keeping
> >>> compatibility code for them.
> >>>
> >>> Remove all old pc-q35 machine classes and keep only pc-q35-2.4.
> >> 
> >> But doesn't that mean that anyone who has a machine configured with one
> >> of those machine types will suddenly find it wont start?
> >> 
> >> Dave
> >> 
> >
> > To some extent, all versions of this board prior to 2.4 should be
> > considered unsupported and we should discourage their use anyway.
> >
> > If you really want, I suppose we could just alias them to 2.4 ...
> 
> I'd very much prefer an honest "won't start" over a silent change of the
> machine type.
> 
> If we really want to bend over backwards for existing uses of these
> machine types, we could make them error out with "use pc-q35-2.5
> instead".  Since I don't think they exist outside testing, I wouldn't
> bother.

Agreed, we should be reporting a hard error for any machine types we
have deleted. Or if we care about smooth upgrade path then we shouldn't
be deleting them in the first place. Silently changing the user's
requested machine type into a different machine type is violating
the semantics of stable machine types.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  parent reply	other threads:[~2015-08-25 16:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 23:11 [Qemu-devel] [PATCH] q35: Remove old machine versions Eduardo Habkost
2015-08-19  9:55 ` Dr. David Alan Gilbert
2015-08-19 16:30   ` Eduardo Habkost
2015-08-25  9:42     ` Michael S. Tsirkin
2015-08-25 16:16       ` John Snow
2015-08-27 10:50         ` Michael S. Tsirkin
2015-08-19 18:16   ` John Snow
2015-08-24  9:54     ` Markus Armbruster
2015-08-24 18:46       ` John Snow
2015-08-25  8:51       ` Marcel Apfelbaum
2015-08-25 16:21       ` Daniel P. Berrange [this message]
2015-08-27 10:50         ` Michael S. Tsirkin
2015-08-27 11:01           ` Daniel P. Berrange
2015-08-27 11:05             ` Michael S. Tsirkin
2015-08-27 13:16               ` Daniel P. Berrange
2015-08-27 18:26           ` Eduardo Habkost
2015-08-28 10:00             ` Markus Armbruster
2015-08-28 17:18               ` Eduardo Habkost
2015-08-21 17:06 ` Laszlo Ersek
2015-09-11 18:44 ` Eduardo Habkost
2015-09-11 19:19   ` Markus Armbruster
2015-09-13  9:28   ` Michael S. Tsirkin
2015-09-14  7:18     ` Markus Armbruster
2015-09-14 15:09     ` Eric Blake
2015-09-14 19:43       ` Eduardo Habkost
2015-09-15  6:03         ` Markus Armbruster

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=20150825162116.GD25920@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@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 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).