qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Cc: Marcel Apfelbaum <marcel.a@redhat.com>,
	qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] q35: Remove old machine versions
Date: Tue, 25 Aug 2015 12:16:04 -0400	[thread overview]
Message-ID: <55DC94C4.6000205@redhat.com> (raw)
In-Reply-To: <20150825124140-mutt-send-email-mst@redhat.com>



On 08/25/2015 05:42 AM, Michael S. Tsirkin wrote:
> On Wed, Aug 19, 2015 at 09:30:20AM -0700, Eduardo Habkost wrote:
>> On Wed, Aug 19, 2015 at 10:55:26AM +0100, 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?
>>
>> Yes, and they will have to update their configuration to use pc-q35-2.4
>> or newer.
> 
> That seems easily avoidable: just make pc-q35-X alias pc-q35-2.4 for X < 2.4.
> 

Both Marcel and Markus would prefer it to fail outright instead of
silently perform magic, in response to my suggesting the same thing.

>> -- 
>> Eduardo

  reply	other threads:[~2015-08-25 16:16 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 [this message]
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
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=55DC94C4.6000205@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@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).