From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Prasad Pandit <ppandit@redhat.com>,
Juraj Marcin <jmarcin@redhat.com>,
berrange@redhat.com, Marco Cavenati <Marco.Cavenati@eurecom.fr>
Subject: Re: [PATCH 0/4] migration: savevm testing
Date: Thu, 27 Mar 2025 11:46:56 -0300 [thread overview]
Message-ID: <87a596a5un.fsf@suse.de> (raw)
In-Reply-To: <20250327143934.7935-1-farosas@suse.de>
Fabiano Rosas <farosas@suse.de> writes:
> Hi, we had a bug report that enabling multifd and attempting
> savevm/loadvm crashes QEMU. This seems to have been around for many
> years.
>
> I'm adding a fix for this in the form of a capabilities check for
> snapshots.
>
> I'm also adding a couple of tests that validate migration capabilities
> are properly rejected by savevm.
>
> There is a larger discussion to be had which is whether we want to
> attempt to implement every migration capability for snapshots or
> should we try to convert snapshots into a regular migration or some
> third option. For now I'm trying to avoid this by not touching
> capabilities that don't cause a crash, but let me know your thoughts.
Turns out, there's a patch that just arrived on the mailing list adding
mapped-ram support for savevm/loadvm, so I guess we'll have this
discussion now =)
migration: add FEATURE_SEEKABLE to QIOChannelBlock
https://lore.kernel.org/r/20250327141451.163744-3-Marco.Cavenati@eurecom.fr
>
> Thanks
>
> CI run: https://gitlab.com/farosas/qemu/-/pipelines/1738368896
>
> Fabiano Rosas (4):
> migration/savevm: Add a compatibility check for capabilities
> tests/qtest/migration: Extract machine type resolution
> tests/qtest/migration: Add QMP helpers for snapshot
> tests/qtest/migration: Add savevm tests
>
> migration/options.c | 26 +++++
> migration/options.h | 1 +
> migration/savevm.c | 8 ++
> tests/qtest/meson.build | 1 +
> tests/qtest/migration-test.c | 1 +
> tests/qtest/migration/framework.c | 54 ++++++----
> tests/qtest/migration/framework.h | 5 +
> tests/qtest/migration/migration-qmp.c | 120 +++++++++++++++++++++
> tests/qtest/migration/migration-qmp.h | 4 +
> tests/qtest/migration/savevm-tests.c | 144 ++++++++++++++++++++++++++
> 10 files changed, 345 insertions(+), 19 deletions(-)
> create mode 100644 tests/qtest/migration/savevm-tests.c
prev parent reply other threads:[~2025-03-27 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 14:39 [PATCH 0/4] migration: savevm testing Fabiano Rosas
2025-03-27 14:39 ` [PATCH 1/4] migration/savevm: Add a compatibility check for capabilities Fabiano Rosas
2025-03-27 14:54 ` Daniel P. Berrangé
2025-03-27 15:11 ` Fabiano Rosas
2025-04-04 20:26 ` Fabiano Rosas
2025-04-07 12:14 ` Fabiano Rosas
2025-04-11 19:23 ` Fabiano Rosas
2025-03-27 16:46 ` Marco Cavenati
2025-03-27 17:02 ` Fabiano Rosas
2025-03-27 14:39 ` [PATCH 2/4] tests/qtest/migration: Extract machine type resolution Fabiano Rosas
2025-03-27 14:39 ` [PATCH 3/4] tests/qtest/migration: Add QMP helpers for snapshot Fabiano Rosas
2025-03-27 14:39 ` [PATCH 4/4] tests/qtest/migration: Add savevm tests Fabiano Rosas
2025-03-27 14:46 ` Fabiano Rosas [this message]
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=87a596a5un.fsf@suse.de \
--to=farosas@suse.de \
--cc=Marco.Cavenati@eurecom.fr \
--cc=berrange@redhat.com \
--cc=jmarcin@redhat.com \
--cc=peterx@redhat.com \
--cc=ppandit@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.