From: Steven Sistare <steven.sistare@oracle.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>,
Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
"Dr. David Alan Gilbert" <dave@treblig.org>,
Cedric Le Goater <clg@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH V5 00/19] Live update: cpr-exec
Date: Wed, 1 Oct 2025 15:24:44 -0400 [thread overview]
Message-ID: <d91186b6-24d9-4b3a-a4c5-d68445c267bb@oracle.com> (raw)
In-Reply-To: <c7ae8d4a-05ee-48fe-8edd-77dffecf2c32@oracle.com>
On 10/1/2025 3:07 PM, Steven Sistare wrote:
> On 10/1/2025 2:56 PM, Peter Xu wrote:
>> On Wed, Oct 01, 2025 at 08:33:52AM -0700, Steve Sistare wrote:
>>> This patch series adds the live migration cpr-exec mode.
>>>
>>> The new user-visible interfaces are:
>>> * cpr-exec (MigMode migration parameter)
>>> * cpr-exec-command (migration parameter)
>>>
>>> cpr-exec mode is similar in most respects to cpr-transfer mode, with the
>>> primary difference being that old QEMU directly exec's new QEMU. The user
>>> specifies the command to exec new QEMU in the migration parameter
>>> cpr-exec-command.
>>
>> It turns out I was right where I replied to patch 5; this fails the Windows
>> build.
>>
>> Smallest fix is to wrap qemu_memfd_create() with a CONFIG_LINUX ifdef,
>> returning -1 to mfd otherwise.
>
> That does not make sense. It already does that, which is why I used it:
>
> util/memfd.c
>
> int qemu_memfd_create(const char *name, size_t size, bool hugetlb,
> uint64_t hugetlbsize, unsigned int seals, Error **errp)
> {
> ...
> #ifdef CONFIG_LINUX
> ...
> return mfd;
> #else
> error_setg_errno(errp, ENOSYS, "failed to create memfd");
> #endif
> return -1;
> }
>
> Did the windows build fail due to a different error?
>
>> A better one is we only include cpr*.c in meson.build if it's linux.
>> Personally I'm OK if we go with the smaller one as of now, however then it
>> would definitely be nice to have a follow up series to reach the better
>> solution, if that makes sense.
>>
>> Feel free to use "make docker-test-build@fedora-win64-cross" for verifying
>> the changes. I hope it'll work for you, even if for me currently it didn't
>> work due to a gitlab.com dns resolution pulling dtc src, where I didn't dig
>> deeper yet..
>>
>> The other thing is, this series doesn't apply on master branch. I didn't
>> feel confident to do it myself on the vfio change, please have a look on
>> both issues.
> Ugh, they renamed everything. I will rebase and send V6.
Actually that was easy to resolve, not worth a V6?
In patch "vfio: cpr-exec mode", drop the change in container.c, and instead
add MIG_MODE_CPR_EXEC to container-legacy.c here:
if (migrate_add_blocker_modes(&vbasedev->cpr.mdev_blocker, errp,
MIG_MODE_CPR_TRANSFER, MIG_MODE_CPR_EXEC,
-1) < 0) {
- Steve
next prev parent reply other threads:[~2025-10-01 19:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 15:33 [PATCH V5 00/19] Live update: cpr-exec Steve Sistare
2025-10-01 15:33 ` [PATCH V5 01/19] migration: multi-mode notifier Steve Sistare
2025-10-01 15:33 ` [PATCH V5 02/19] migration: add cpr_walk_fd Steve Sistare
2025-10-01 15:33 ` [PATCH V5 03/19] oslib: qemu_clear_cloexec Steve Sistare
2025-10-01 15:33 ` [PATCH V5 04/19] migration: cpr-exec-command parameter Steve Sistare
2025-10-01 15:33 ` [PATCH V5 05/19] migration: cpr-exec save and load Steve Sistare
2025-10-01 16:36 ` Peter Xu
2025-10-01 15:33 ` [PATCH V5 06/19] migration: cpr-exec mode Steve Sistare
2025-10-01 15:33 ` [PATCH V5 07/19] migration: cpr-exec docs Steve Sistare
2025-10-01 15:34 ` [PATCH V5 08/19] vfio: cpr-exec mode Steve Sistare
2025-10-01 15:34 ` [PATCH V5 09/19] tests/qtest: export qtest_qemu_binary Steve Sistare
2025-10-01 15:34 ` [PATCH V5 10/19] tests/qtest: qtest_qemu_args Steve Sistare
2025-10-01 15:34 ` [PATCH V5 11/19] tests/qtest: qtest_create_test_state Steve Sistare
2025-10-01 15:34 ` [PATCH V5 12/19] tests/qtest: qtest_qemu_spawn_func Steve Sistare
2025-10-01 15:34 ` [PATCH V5 13/19] tests/qtest: qtest_init_after_exec Steve Sistare
2025-10-01 15:34 ` [PATCH V5 14/19] migration-test: only_source option Steve Sistare
2025-10-01 15:34 ` [PATCH V5 15/19] migration-test: shm path accessor Steve Sistare
2025-10-01 15:34 ` [PATCH V5 16/19] migration-test: misc exports Steve Sistare
2025-10-01 15:34 ` [PATCH V5 17/19] migration-test: migrate_args Steve Sistare
2025-10-01 15:34 ` [PATCH V5 18/19] migration-test: strv parameter Steve Sistare
2025-10-01 15:34 ` [PATCH V5 19/19] migration-test: test cpr-exec Steve Sistare
2025-10-01 18:56 ` [PATCH V5 00/19] Live update: cpr-exec Peter Xu
2025-10-01 19:07 ` Steven Sistare
2025-10-01 19:24 ` Steven Sistare [this message]
2025-10-01 20:05 ` Peter Xu
2025-10-02 12:44 ` Steven Sistare
2025-10-02 8:48 ` Cédric Le Goater
2025-10-01 20:03 ` Peter Xu
2025-10-02 8:50 ` Cédric Le Goater
2025-10-02 13:45 ` Steven Sistare
2025-10-02 13:44 ` Steven Sistare
2025-10-03 11:36 ` Steven Sistare
2025-10-03 13:11 ` Peter Xu
2025-10-03 13:36 ` Steven Sistare
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=d91186b6-24d9-4b3a-a4c5-d68445c267bb@oracle.com \
--to=steven.sistare@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=clg@redhat.com \
--cc=dave@treblig.org \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=pbonzini@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).