From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: agraf@suse.de, stefanb@linux.vnet.ibm.com,
Markus Armbruster <armbru@redhat.com>,
quintela@redhat.com, qemu-devel@nongnu.org,
mdroth@linux.vnet.ibm.com, aliguori@amazon.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format
Date: Tue, 6 May 2014 23:26:12 +0300 [thread overview]
Message-ID: <20140506202612.GA15229@redhat.com> (raw)
In-Reply-To: <20140506185807.GB8277@work-vm>
On Tue, May 06, 2014 at 07:58:07PM +0100, Dr. David Alan Gilbert wrote:
> * Markus Armbruster (armbru@redhat.com) wrote:
> > "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> <snip>
>
> > > OK but for a new machine type, let's default to BER, right?
> > > I see no reason to keep supporting when non-BER when -M specifies 2.1
> > > compatibility, do you?
> >
> > I fail to see the relation between machine type and migration's wire
> > encoding.
>
> New machine types are a useful but not definitive line in the sand. If
> you enable something/change the default on a new machine type you know
> it won't break any existing users since there aren't any.
>
> Dve
Exactly. And on the other hand, someone enabling old machine type
and doing live migration is likely to want to be compatible with old
qemu wrt migration.
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-05-06 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398271069-22057-1-git-send-email-dgilbert@redhat.com>
[not found] ` <1398271069-22057-6-git-send-email-dgilbert@redhat.com>
2014-05-07 9:47 ` [Qemu-devel] [RFC PATCH v2 05/16] Header/constant/types fixes for visitors Michael S. Tsirkin
2014-05-07 10:33 ` Dr. David Alan Gilbert
[not found] ` <1398271069-22057-2-git-send-email-dgilbert@redhat.com>
2014-05-07 9:50 ` [Qemu-devel] [RFC PATCH v2 01/16] Visitor: Add methods for migration format use Michael S. Tsirkin
2014-05-07 10:23 ` Dr. David Alan Gilbert
2014-05-07 10:32 ` Michael S. Tsirkin
[not found] ` <5357EF56.4010703@redhat.com>
[not found] ` <20140423171622.GG2516@work-vm>
[not found] ` <87sip3dvsj.fsf@blackfin.pond.sub.org>
[not found] ` <20140424082059.GB2459@work-vm>
[not found] ` <20140424082923.GA31845@redhat.com>
[not found] ` <87wqeduc0d.fsf@blackfin.pond.sub.org>
2014-05-06 18:58 ` [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format Dr. David Alan Gilbert
2014-05-06 20:26 ` Michael S. Tsirkin [this message]
2014-05-07 5:49 ` Markus Armbruster
2014-05-07 9:22 ` Dr. David Alan Gilbert
[not found] ` <5357FCA9.8040801@redhat.com>
[not found] ` <20140423175410.GA28308@redhat.com>
[not found] ` <53580D27.2080507@redhat.com>
2014-05-07 9:57 ` Michael S. Tsirkin
[not found] ` <1398271069-22057-16-git-send-email-dgilbert@redhat.com>
2014-05-07 10:02 ` [Qemu-devel] [RFC PATCH v2 15/16] Wire in BER visitors Michael S. Tsirkin
2014-05-07 10:08 ` Dr. David Alan Gilbert
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=20140506202612.GA15229@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanb@linux.vnet.ibm.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).