From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com, qemu-stable <qemu-stable@nongnu.org>,
"Peter Krempa" <pkrempa@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] migration: Allow pipes to keep working for fd migrations
Date: Thu, 21 Nov 2024 10:04:21 -0300 [thread overview]
Message-ID: <87ed34sppm.fsf@suse.de> (raw)
In-Reply-To: <20241120160132.3659735-1-peterx@redhat.com>
Peter Xu <peterx@redhat.com> writes:
> Libvirt may still use pipes for old file migrations in fd: URI form,
> especially when loading old images dumped from Libvirt's compression
> algorithms.
>
> In that case, Libvirt needs to compress / uncompress the images on its own
> over the migration binary stream, and pipes are passed over to QEMU for
> outgoing / incoming migrations in "fd:" URIs.
>
> For future such use case, it should be suggested to use mapped-ram when
> saving such VM image. However there can still be old images that was
> compressed in such way, so libvirt needs to be able to load those images,
> uncompress them and use the same pipe mechanism to pass that over to QEMU.
>
> It means, even if new file migrations can be gradually moved over to
> mapped-ram (after Libvirt start supporting it), Libvirt still needs the
> uncompressor for the old images to be able to load like before.
>
> Meanwhile since Libvirt currently exposes the compression capability to
> guest images, it may needs its own lifecycle management to move that over
> to mapped-ram, maybe can be done after mapped-ram saved the image, however
> Dan and PeterK raised concern on temporary double disk space consumption.
> I suppose for now the easiest is to enable pipes for both sides of "fd:"
> migrations, until all things figured out from Libvirt side on how to move
> on.
>
> And for "channels" QMP interface support on "migrate" / "migrate-incoming"
> commands, we'll also need to move away from pipe. But let's leave that for
> later too.
>
> So far, still allow pipes to happen like before on both save/load sides,
> just like we would allow sockets to pass.
>
> Cc: qemu-stable <qemu-stable@nongnu.org>
> Cc: Fabiano Rosas <farosas@suse.de>
> Cc: Peter Krempa <pkrempa@redhat.com>
> Cc: Daniel P. Berrangé <berrange@redhat.com>
> Fixes: c55deb860c ("migration: Deprecate fd: for file migration")
> Signed-off-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
prev parent reply other threads:[~2024-11-21 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 16:01 [PATCH] migration: Allow pipes to keep working for fd migrations Peter Xu
2024-11-21 13:04 ` 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=87ed34sppm.fsf@suse.de \
--to=farosas@suse.de \
--cc=berrange@redhat.com \
--cc=peterx@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).