From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
jes sorensen <jes.sorensen@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] migration: new sections and backward compatibility.
Date: Thu, 07 Jul 2011 17:23:52 +0200 [thread overview]
Message-ID: <4E15CF88.8080404@redhat.com> (raw)
In-Reply-To: <A1A7637F-D89B-4F20-8299-1105AE870967@suse.de>
On 07/07/2011 01:02 PM, Alexander Graf wrote:
> I'd guess the best would be to have a special VMSTATE that means
> "broken old version doesn't send a section" which we can set for
> special -M?
No, the best would be to have a serious migration format, based for
example on ASN.1 which Michael Tsirkin was playing with. We cannot keep
bolting more and more stuff on top of the current protocol, especially
since adding a new protocol is not that hard (old machine types can keep
the old protocol).
> That would of course not help with RHEL:).
At least for RHEL6 we can live with adding a few hacks here and there.
Paolo
next prev parent reply other threads:[~2011-07-07 15:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:04 [Qemu-devel] migration: new sections and backward compatibility Gerd Hoffmann
2011-07-06 17:13 ` Anthony Liguori
2011-07-07 7:19 ` Gerd Hoffmann
2011-07-07 15:36 ` Anthony Liguori
2011-07-12 14:50 ` Gerd Hoffmann
2011-07-07 9:23 ` Markus Armbruster
2011-07-07 11:02 ` Alexander Graf
2011-07-07 15:23 ` Paolo Bonzini [this message]
2011-07-11 15:32 ` Kevin Wolf
2011-07-11 15:31 ` Paolo Bonzini
2011-07-07 14:40 ` Gerd Hoffmann
2011-07-07 15:37 ` Anthony Liguori
2011-07-07 16:44 ` Markus Armbruster
2011-07-06 17:28 ` Avi Kivity
2011-07-06 20:01 ` Anthony Liguori
2011-07-06 23:32 ` Alexander Graf
2011-07-07 7:14 ` Gerd Hoffmann
2011-07-07 7:30 ` Avi Kivity
2011-07-08 13:02 ` Jes Sorensen
2011-07-08 14:43 ` Peter Maydell
2011-07-08 15:12 ` Gerd Hoffmann
2011-07-07 15:33 ` Anthony Liguori
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=4E15CF88.8080404@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=jes.sorensen@redhat.com \
--cc=kraxel@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).