[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format
From: |
Eric Blake |
Subject: |
Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format |
Date: |
Wed, 23 Apr 2014 10:50:30 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 |
On 04/23/2014 10:37 AM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <address@hidden>
>
> 4) At the moment you select BER output format by setting an environment
> variable ( export QEMUMIGFORMAT=BER ) , I need to put more thought
> in to the right way to do this, there are some harder questions like
> what happens to devices that are still using pre-vmstate encodings
> (that are currently sent as blobs) when they eventually convert over
> and thus how to keep compatibility with earlier BER output versions
> where they were blobs.
I don't have good advice on how to address intra-version design (what
happens when an old version of BER sends a blob but a new version on the
receiving side expects formatted data instead of a blob), other than
it's going to be similar to any other intra-version design that we
already have to consider when upgrading from old to new qemu.
But for how to select BER format, I _do_ have an idea:
https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg00782.html
Basically, I think that the choice of migration format should be
selected via a new extended capability added to
migrate-set-capabilities. Setting the choice at the environment
variable is too inflexible (it's locked down for the duration of the
entire qemu process), whereas setting it via QMP is desirable (for
example, it would let us choose at the time of migration whether we are
migrating to an older host and want the old format, or migrating to a
file for checkpointing reasons and want the new format).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- [Qemu-devel] [RFC PATCH v2 07/16] Visitor: Binary compatible input visitor, (continued)
- [Qemu-devel] [RFC PATCH v2 07/16] Visitor: Binary compatible input visitor, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 09/16] Visitor: Load path, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 10/16] Visitor: Common types to use visitors, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 11/16] BER Visitor: Create output visitor, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 14/16] ASN.1 schema for new migration format, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 13/16] Start some BER format docs, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 16/16] Add vmstate_cpu_common BER type code and wire it in., Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 04/16] qemu-file: Add set/get tmp_visitor, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 08/16] Visitor: Output path, Dr. David Alan Gilbert (git), 2014/04/23
- [Qemu-devel] [RFC PATCH v2 12/16] BER Visitor: Create input visitor, Dr. David Alan Gilbert (git), 2014/04/23
- Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format,
Eric Blake <=
- Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format, Markus Armbruster, 2014/04/24
- Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format, Dr. David Alan Gilbert, 2014/04/24
- Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format, Michael S. Tsirkin, 2014/04/24
- Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format, Markus Armbruster, 2014/04/25
- Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format, Eric Blake, 2014/04/25