From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: new->old version migration
Date: Mon, 07 Feb 2011 13:33:57 -0600 [thread overview]
Message-ID: <4D504925.3000807@codemonkey.ws> (raw)
In-Reply-To: <20110207160751.GC25106@redhat.com>
On 02/07/2011 10:07 AM, Michael S. Tsirkin wrote:
> New thread stated intentionally, the original patch is Message-ID:
> <349e93a4cfc6e1effc1b681cae53f805fdb9624e.1296713825.git.amit.shah@redhat.com>
>
> On Thu, Feb 03, 2011 at 11:47:08AM +0530, Amit Shah wrote:
>
>> Add a compat property for older machine types. When this is used (via
>> -M pc-0.13, for example), the new flow control mechanisms will not be
>> used. This is done to keep migration from a machine started with older
>> type on a pc-0.14+ qemu to an older machine working.
>>
>> The property is named 'flow_control' and defaults to on.
>>
>> Reported-by: Alex Williamson<alex.williamson@redhat.com>
>> Signed-off-by: Amit Shah<amit.shah@redhat.com>
>>
> So, I think there are two things that need to be agreed on:
>
> - Can we commit to support migration from new qemu version to an old one?
> We haven't in the past but downstreams do want this,
> so it makes sense to have the infrastructure upstream.
>
Only within a stable release series and only when it's possible without
sacrificing integrity. I know some downstreams disagree with this but I
don't think this is a business we want to get into.
Regards,
Anthony Liguori
> - The infrastructure/command line option for such support.
> We have the -M flags to describe the machine that
> we are running, but that abstracts away guest-visible machine,
> which the migration format is not.
> Also, same qemu could migrate to any older version.
> So I think we would have to add a flag (call it -V for now)
> to savevm/migrate commands to specify the format to be used.
> Naturally some machines would be incompatible with
> specific -V values, that's nothing new.
>
> Pls comment.
>
>
next prev parent reply other threads:[~2011-02-07 21:08 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 [this message]
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
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=4D504925.3000807@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).