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>
Subject: Re: [PATCH v3 2/3] migration/docs: How to migrate when hosts have different features
Date: Tue, 17 Oct 2023 16:05:33 +0200 [thread overview]
Message-ID: <871qdt1h02.fsf@secure.mitica> (raw)
In-Reply-To: <ZGQW7W8i+y9/KpO1@x1n> (Peter Xu's message of "Tue, 16 May 2023 19:51:09 -0400")
Peter Xu <peterx@redhat.com> wrote:
> On Mon, May 15, 2023 at 10:32:00AM +0200, Juan Quintela wrote:
>> +$ qemu-system-x86_64 -cpu host,pcid=off,stibp=off
>> +
>> +Host B:
>> +
>> +$ qemu-system-x86_64 -cpu host,taa-no=off
>
> Since we're using cpu as example, shall we at least mention at the end that
> we don't suggest using -cpu host if migration is needed?
Added something like that.
>> +
>> +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
>> +features in general.
>> +
>> +Other devices have worse control about individual features. If they
>> +want to be able to migrate between hosts that show different features,
>> +the device needs a way to configure which ones it is going to use.
>> +
>> +In this section we have considered that we are using the same QEMU
>> +binary in both sides of the migration. If we use different QEMU
>> +versions process, then we need to have into account all other
>> +differences and the examples become even more complicated.
>
> Mostly good to me. What I worry is how much help this will bring to
> developers - I'd assume developers working on these will be aware of this.
> But I guess it's always good to have any documentation than nothing.
I have two hopes here:
- when developer finds a problem with migration, they look there.
- having a document that I can point when one of this problems happens.
What I do now is that I write an email, normally of worse quality and
not finding a good example.
> Acked-by: Peter Xu <peterx@redhat.com>
Thanks, Juan.
next prev parent reply other threads:[~2023-10-17 14:06 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
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 [this message]
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=871qdt1h02.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 \
/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.