From: Peter Xu <peterx@redhat.com>
To: Alexandr Moshkov <dtalexundeer@yandex-team.ru>
Cc: qemu-devel@nongnu.org, "Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Zhenwei Pi" <pizhenwei@bytedance.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Raphael Norwitz" <raphael@enfabrica.net>,
"Kevin Wolf" <kwolf@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
mzamazal@redhat.com, "Fabiano Rosas" <farosas@suse.de>,
qemu-block@nongnu.org, virtio-fs@lists.linux.dev,
"yc-core@yandex-team.ru" <yc-core@yandex-team.ru>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PATCH v6 5/5] vhost-user-blk: support inter-host inflight migration
Date: Wed, 14 Jan 2026 07:26:24 -0500 [thread overview]
Message-ID: <aWeLcDtZyRpk81W6@x1.local> (raw)
In-Reply-To: <20260113095813.134810-6-dtalexundeer@yandex-team.ru>
On Tue, Jan 13, 2026 at 02:58:19PM +0500, Alexandr Moshkov wrote:
> 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, with feature flag the vhost-user
> back-end can immediately stop vrings, so all in-flight requests will be
> migrated to another host.
>
> Signed-off-by: Alexandr Moshkov <dtalexundeer@yandex-team.ru>
> ---
> hw/block/vhost-user-blk.c | 28 ++++++++++++++++++++++++++++
> include/hw/virtio/vhost-user-blk.h | 1 +
> 2 files changed, 29 insertions(+)
>
> diff --git a/hw/block/vhost-user-blk.c b/hw/block/vhost-user-blk.c
> index a8fd90480a..9093e98841 100644
> --- a/hw/block/vhost-user-blk.c
> +++ b/hw/block/vhost-user-blk.c
> @@ -377,6 +377,7 @@ static int vhost_user_blk_init(DeviceState *dev, bool connect, Error **errp)
> vhost_dev_set_config_notifier(&s->dev, &blk_ops);
>
> s->vhost_user.supports_config = true;
> + s->vhost_user.supports_inflight_migration = s->inflight_migration;
> ret = vhost_dev_init(&s->dev, &s->vhost_user, VHOST_BACKEND_TYPE_USER, 0,
> false, errp);
> if (ret < 0) {
> @@ -656,6 +657,27 @@ static struct vhost_dev *vhost_user_blk_get_vhost(VirtIODevice *vdev)
> return &s->dev;
> }
>
> +static bool vhost_user_blk_inflight_needed(void *opaque)
> +{
> + struct VHostUserBlk *s = opaque;
> +
> + bool inflight_migration = vhost_dev_has_feature(&s->dev,
> + VHOST_USER_PROTOCOL_F_GET_VRING_BASE_INFLIGHT);
> +
> + return inflight_migration &&
> + !migrate_local_vhost_user_blk();
Here's the spot that should depend on migrate_local_vhost_user_blk() from
Vladimilr's RFC patch (again, likely to be renamed..).
Btw, is this check correct against "!migrate_local_vhost_user_blk()"? I
was expecting the feature off only if local=on, so I expect it to be:
return inflight_migration && migrate_local_vhost_user_blk();
?
> +}
> +
> +static const VMStateDescription vmstate_vhost_user_blk_inflight = {
> + .name = "vhost-user-blk/inflight",
> + .version_id = 1,
> + .needed = vhost_user_blk_inflight_needed,
> + .fields = (const VMStateField[]) {
> + VMSTATE_VHOST_INFLIGHT_REGION(inflight, VHostUserBlk),
One other trivial nitpick while glimpsing over the patch: should we move
the macro definition from previous patch to this one, where it is used?
> + VMSTATE_END_OF_LIST()
> + },
> +};
> +
> static bool vhost_user_blk_pre_incoming(void *opaque, Error **errp)
> {
> VHostUserBlk *s = VHOST_USER_BLK(opaque);
> @@ -678,6 +700,10 @@ static const VMStateDescription vmstate_vhost_user_blk = {
> VMSTATE_VIRTIO_DEVICE,
> VMSTATE_END_OF_LIST()
> },
> + .subsections = (const VMStateDescription * const []) {
> + &vmstate_vhost_user_blk_inflight,
> + NULL
> + }
> };
>
> static bool vhost_user_needed(void *opaque)
> @@ -751,6 +777,8 @@ static const Property vhost_user_blk_properties[] = {
> VIRTIO_BLK_F_WRITE_ZEROES, true),
> DEFINE_PROP_BOOL("skip-get-vring-base-on-force-shutdown", VHostUserBlk,
> skip_get_vring_base_on_force_shutdown, false),
> + DEFINE_PROP_BOOL("inflight-migration", VHostUserBlk,
> + inflight_migration, false),
> };
>
> static void vhost_user_blk_class_init(ObjectClass *klass, const void *data)
> diff --git a/include/hw/virtio/vhost-user-blk.h b/include/hw/virtio/vhost-user-blk.h
> index b06f55fd6f..e1466e5cf6 100644
> --- a/include/hw/virtio/vhost-user-blk.h
> +++ b/include/hw/virtio/vhost-user-blk.h
> @@ -52,6 +52,7 @@ struct VHostUserBlk {
> bool started_vu;
>
> bool skip_get_vring_base_on_force_shutdown;
> + bool inflight_migration;
>
> bool incoming_backend;
> };
> --
> 2.34.1
>
--
Peter Xu
next prev parent reply other threads:[~2026-01-14 12:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 9:58 [PATCH v6 0/5] support inflight migration Alexandr Moshkov
2026-01-13 9:58 ` [PATCH v6 1/5] vhost-user.rst: specify vhost-user back-end action on GET_VRING_BASE Alexandr Moshkov
2026-01-13 9:58 ` [PATCH v6 2/5] vhost-user: introduce protocol feature for skip drain " Alexandr Moshkov
2026-01-13 18:00 ` Stefan Hajnoczi
2026-01-13 9:58 ` [PATCH v6 3/5] vmstate: introduce VMSTATE_VBUFFER_UINT64 Alexandr Moshkov
2026-01-13 9:58 ` [PATCH v6 4/5] vhost: add vmstate for inflight region with inner buffer Alexandr Moshkov
2026-01-14 19:15 ` Peter Xu
2026-01-14 21:38 ` Stefan Hajnoczi
2026-01-14 21:57 ` Peter Xu
2026-01-13 9:58 ` [PATCH v6 5/5] vhost-user-blk: support inter-host inflight migration Alexandr Moshkov
2026-01-14 12:26 ` Peter Xu [this message]
2026-01-13 18:12 ` [PATCH v6 0/5] support " Stefan Hajnoczi
2026-01-13 18:56 ` Peter Xu
2026-01-14 6:19 ` Vladimir Sementsov-Ogievskiy
2026-01-14 12:22 ` Peter Xu
2026-01-14 14:35 ` Vladimir Sementsov-Ogievskiy
2026-01-14 15:17 ` Peter Xu
2026-01-14 17:54 ` Vladimir Sementsov-Ogievskiy
2026-01-14 19:10 ` Peter Xu
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=aWeLcDtZyRpk81W6@x1.local \
--to=peterx@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=dtalexundeer@yandex-team.ru \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=mzamazal@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael@enfabrica.net \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-fs@lists.linux.dev \
--cc=yc-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox