From: Juan Quintela <quintela@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, "Leonardo Bras" <leobras@redhat.com>,
"Peter Xu" <peterx@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:11:18 +0200 [thread overview]
Message-ID: <87wmvlz6d5.fsf@secure.mitica> (raw)
In-Reply-To: <20230517062128-mutt-send-email-mst@kernel.org> (Michael S. Tsirkin's message of "Wed, 17 May 2023 06:23:26 -0400")
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Mon, May 15, 2023 at 10:32:00AM +0200, Juan Quintela wrote:
>> Sometimes devices have different features depending of things outside
>> of qemu. For instance the kernel. Document how to handle that cases.
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>
> yes, e.g. vhost features are exactly like this.
Yeap, I know that. But not in enough detail to get a good example.
[...]
>> +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.
>
> How do people know what to do?
They need to:
- know their hardware/device/driver.
- how they can do it in qemu.
I can help with the second, not with the 1st.
> How about a tool that will help you get data from hosts
> and then tell you how to configure qemu to make them
> compatible?
This is the holy gray of migration. I would like to be able to create
machines from QMP. That way, I can transport the configuration over the
migration channel, instead of hoping that it is the same. Troubles so
far:
- we are very far away of being able to create machines with QMP (not
migration related).
- we have properties that can be different on source and destination.
For instance, the path to the file that implements a device can be
different on both systems.
We could add some keyword to the part of the configuration that can be
different. As said, we can say that destination/QMP can give us a new
path for a block device. But we need to be able to mark number of
CPU's as required to be the same.
- For devices/state that can't be seen from inside qemu, I don't know
have a good idea. It can be related that I am not an expert on that
type of devices. Perhaps someone that knows more about they can give
some insights.
Later, Juan.
next prev parent reply other threads:[~2023-10-17 14:11 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
2023-05-17 10:23 ` Michael S. Tsirkin
2023-10-17 14:11 ` Juan Quintela [this message]
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=87wmvlz6d5.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 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).