From: Juan Quintela <quintela@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: Re: [PATCH v2 2/3] migration/doc: How to migrate when hosts have different features
Date: Wed, 18 Oct 2023 12:44:07 +0200 [thread overview]
Message-ID: <877cnkxlag.fsf@secure.mitica> (raw)
In-Reply-To: <87mswhw5vn.fsf@suse.de> (Fabiano Rosas's message of "Tue, 17 Oct 2023 13:50:04 -0300")
Fabiano Rosas <farosas@suse.de> wrote:
> Juan Quintela <quintela@redhat.com> writes:
>> +Notice that this is not completely related to QEMU. The most
>> +important thing here is that this should be handle by the managing
>
> s/handle/handled/
Done.
>> +application that launches QEMU. If QEMU is configured correctly, the
>> +migration will suceeed.
>
> s/suceeed/succeed/
Done.
>
>> +
>> +Once that we have defined that, doing this is complicated. Almost all
>
> I get what you mean here, but it is slightly confusing. Maybe
>
> "Once we have defined that, doing it is complicated." or
> "That said, actually doing it is complicated."
Last one wins.
>> +When both hosts have different cpu features this is waranteed to
>> fail.
>
> s/waranteed/guaranteed/
Done.
>> +And you would be able to migrate between them. It is responsability
>> +of the management application or of the user to make sure that the
>> +configuration is correct. QEMU don't know how to look at this kind of
>
> s/don't/doesn't/
Done
>> +features in general.
>> +
>> +Notice that we don't recomend to use -cpu host for migration. It is
>> +used in this example because it makes the exampler simpler.
>
> s/exampler/example/
Thanks.
next prev parent reply other threads:[~2023-10-18 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 15:18 [PATCH v2 0/3] Migration Documentation for backward compatibility Juan Quintela
2023-10-17 15:18 ` [PATCH v2 1/3] migration/doc: Add documentation for backwards compatiblity Juan Quintela
2023-10-17 16:20 ` Peter Maydell
2023-10-18 11:24 ` Juan Quintela
2023-10-17 15:18 ` [PATCH v2 2/3] migration/doc: How to migrate when hosts have different features Juan Quintela
2023-10-17 16:50 ` Fabiano Rosas
2023-10-18 10:44 ` Juan Quintela [this message]
2023-10-17 15:18 ` [PATCH v2 3/3] migration/doc: We broke backwards compatibility Juan Quintela
2023-10-17 16:56 ` Fabiano Rosas
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=877cnkxlag.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.