From: Markus Armbruster <armbru@redhat.com>
To: Alexandr Moshkov <dtalexundeer@yandex-team.ru>
Cc: qemu-devel@nongnu.org, Raphael Norwitz <raphael@enfabrica.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Subject: Re: [PATCH 0/2] vhost-user-blk: support inflight migration
Date: Mon, 20 Oct 2025 11:55:15 +0200 [thread overview]
Message-ID: <87a51l99to.fsf@pond.sub.org> (raw)
In-Reply-To: <20251020054413.2614932-1-dtalexundeer@yandex-team.ru> (Alexandr Moshkov's message of "Mon, 20 Oct 2025 10:44:12 +0500")
Alexandr Moshkov <dtalexundeer@yandex-team.ru> writes:
> Hi!
>
> During inter-host migration, waiting for disk requests to be drained
> in the vhost-user backend can incur significant downtime.
>
> This can be avoided if QEMU migrates the inflight region in vhost-user-blk.
> Thus, during the qemu migration, the vhost-user backend can cancel all inflight requests and
> then, after migration, they will be executed on another host.
>
> At first, I tried to implement migration for all vhost-user devices that support inflight at once,
> but this would require a lot of changes both in vhost-user-blk (to transfer it to the base class) and
> in the vhost-user-base base class (inflight implementation and remodeling + a large refactor).
>
> Therefore, for now I decided to leave this idea for later and
> implement the migration of the inflight region first for vhost-user-blk.
How is this work related to Vladimir's "vhost-user-blk: live-backend
local migration"?
next prev parent reply other threads:[~2025-10-20 9:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 5:44 [PATCH 0/2] vhost-user-blk: support inflight migration Alexandr Moshkov
2025-10-20 5:44 ` [PATCH 1/2] vhost: support inflight save/load Alexandr Moshkov
2025-10-21 19:29 ` Peter Xu
2025-10-23 6:46 ` Alexandr Moshkov
2025-10-20 5:44 ` [PATCH 2/2] vhost-user-blk: support inflight migration Alexandr Moshkov
2025-10-20 9:55 ` Markus Armbruster
2025-10-20 10:34 ` Alexandr Moshkov
2025-10-20 11:47 ` Markus Armbruster
2025-10-23 19:24 ` Peter Xu
2025-10-24 8:42 ` Alexandr Moshkov
2025-10-23 14:29 ` Lei Yang
2025-10-24 8:37 ` Alexandr Moshkov
2025-10-25 14:19 ` Lei Yang
2025-10-20 9:55 ` Markus Armbruster [this message]
2025-10-20 10:16 ` [PATCH 0/2] " Alexandr Moshkov
2025-10-21 18:54 ` Raphael Norwitz
2025-10-22 7:59 ` Alexandr Moshkov
2025-10-22 21:33 ` Raphael Norwitz
2025-10-23 6:44 ` Alexandr Moshkov
2025-10-23 17:53 ` Raphael Norwitz
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=87a51l99to.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=dtalexundeer@yandex-team.ru \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=raphael@enfabrica.net \
--cc=sgarzare@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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.