From: Juan Quintela <quintela@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
"Leonardo Bras" <leobras@redhat.com>,
"Jiri Denemark" <jdenemar@redhat.com>,
"Avihai Horon" <avihaih@nvidia.com>,
"Fiona Ebner" <f.ebner@proxmox.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>
Subject: Re: [PATCH v3 1/3] migration: Add documentation for backwards compatiblity
Date: Mon, 23 Oct 2023 13:09:01 +0200 [thread overview]
Message-ID: <875y2xtx2q.fsf@secure.mitica> (raw)
In-Reply-To: <ZGQUMyKBbkLlsDhD@x1n> (Peter Xu's message of "Tue, 16 May 2023 19:39:31 -0400")
Peter Xu <peterx@redhat.com> wrote:
> On Mon, May 15, 2023 at 10:31:59AM +0200, Juan Quintela wrote:
[..]
>> +When we do migration, we have to QEMU process: the source and the
>
> s/to/two/, s/process/processes/
done.
>> +target. There are two cases, they are the same version or they are a
>> +different version.
>
> s/a different version/different versions/
done
>> +The easy case is when they are the same version.
>> +The difficult one is when they are different versions.
>> +
>> +There are two things that are different, but they have very similar
>> +names and sometimes get confused:
>
> (space)
>
>> +- QEMU version
>> +- machine version
>
> It's normally called "machine type", so maybe use that? Or just "machine
> version / machine type"?
machine type version
>
> This is definitely more detailed than I thought. :)
>
> Acked-by: Peter Xu <peterx@redhat.com>
Thanks, Juan.
next prev parent reply other threads:[~2023-10-23 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:31 [PATCH v3 0/3] Migration documentation Juan Quintela
2023-05-15 8:31 ` [PATCH v3 1/3] migration: Add documentation for backwards compatiblity Juan Quintela
2023-05-16 23:39 ` Peter Xu
2023-05-18 1:47 ` Xiaoyao Li
2023-10-17 13:59 ` Juan Quintela
2023-10-23 11:09 ` Juan Quintela [this message]
2023-05-15 8:32 ` [PATCH v3 2/3] migration/docs: How to migrate when hosts have different features Juan Quintela
2023-05-16 23:51 ` Peter Xu
2023-10-17 14:05 ` Juan Quintela
2023-05-17 10:23 ` Michael S. Tsirkin
2023-10-17 14:11 ` Juan Quintela
2023-05-15 8:32 ` [PATCH v3 3/3] migration/doc: We broke backwards compatibility Juan Quintela
2023-05-17 0:03 ` Peter Xu
2023-10-17 14:18 ` Juan Quintela
2023-05-17 7:09 ` Fiona Ebner
2023-10-23 11:09 ` Juan Quintela
2023-05-17 10:20 ` Michael S. Tsirkin
2023-05-17 11:43 ` Juan Quintela
2023-05-17 11:47 ` Michael S. Tsirkin
2023-05-31 13:23 ` 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=875y2xtx2q.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=avihaih@nvidia.com \
--cc=berrange@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=jdenemar@redhat.com \
--cc=leobras@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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).