From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Juan Quintela <quintela@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: new->old version migration
Date: Tue, 08 Feb 2011 01:44:32 -0600 [thread overview]
Message-ID: <4D50F460.5070402@codemonkey.ws> (raw)
In-Reply-To: <20110208070714.GA29281@amit-x200.redhat.com>
On 02/08/2011 01:07 AM, Amit Shah wrote:
> On (Tue) 08 Feb 2011 [08:42:14], Michael S. Tsirkin wrote:
>
>> I see. I'm unhappy with the facts that
>> 1. if (feature) is spread all over the code instead
>> of just in migration
>> 2. it is also obfuscated with if (flow_control)
>> instead of plain if (migrate to qemu< 0.14)
>> so removing it will be much harder
>> 3. this forces anyone who wants
>> a VM compatible with qemu 0.13 to also lose data,
>> even if migration to 0.13 is never attempted.
>>
> If a machine is started with -M pc-0.13 then we can safely assume the
> user will want to migrate to another 0.13 machine.
>
No, a user wants a guest that works. If there was a bug in 0.13 and
it's fixed in 0.14, then reintroducing the bug in -M pc-0.13 is not
expected.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-02-08 7:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 16:07 [Qemu-devel] new->old version migration Michael S. Tsirkin
2011-02-07 16:40 ` [Qemu-devel] " Alex Williamson
2011-02-07 16:51 ` Michael S. Tsirkin
2011-02-07 19:39 ` Anthony Liguori
2011-02-07 19:33 ` Anthony Liguori
2011-02-07 19:53 ` Michael S. Tsirkin
2011-02-07 20:56 ` Anthony Liguori
2011-02-07 21:52 ` Michael S. Tsirkin
2011-02-08 2:23 ` Anthony Liguori
2011-02-08 6:42 ` Michael S. Tsirkin
2011-02-08 7:07 ` Amit Shah
2011-02-08 7:44 ` Anthony Liguori [this message]
2011-02-08 7:54 ` Amit Shah
2011-02-08 7:42 ` Anthony Liguori
2011-02-08 11:19 ` Michael S. Tsirkin
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=4D50F460.5070402@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alex.williamson@redhat.com \
--cc=amit.shah@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).