qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	devel@lists.libvirt.org
Subject: [PATCH 6/6] migration: Deprecate fd: for file migration
Date: Thu, 25 Apr 2024 12:09:39 -0300	[thread overview]
Message-ID: <20240425150939.19268-7-farosas@suse.de> (raw)
In-Reply-To: <20240425150939.19268-1-farosas@suse.de>

The fd: URI can currently trigger two different types of migration, a
TCP migration using sockets and a file migration using a plain
file. This is in conflict with the recently introduced (8.2) QMP
migrate API that takes structured data as JSON-like format. We cannot
keep the same backend for both types of migration because with the new
API the code is more tightly coupled to the type of transport. This
means a TCP migration must use the 'socket' transport and a file
migration must use the 'file' transport.

If we keep allowing fd: when using a file, this creates an issue when
the user converts the old-style (fd:) to the new style ("transport":
"socket") invocation because the file descriptor in question has
previously been allowed to be either a plain file or a socket.

To avoid creating too much confusion, we can simply deprecate the fd:
+ file usage, which is thought to be rarely used currently and instead
establish a 1:1 correspondence between fd: URI and socket transport,
and file: URI and file transport.

Signed-off-by: Fabiano Rosas <farosas@suse.de>
---
 docs/about/deprecated.rst | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
index fadb85f289..11dce324c8 100644
--- a/docs/about/deprecated.rst
+++ b/docs/about/deprecated.rst
@@ -484,3 +484,17 @@ both, older and future versions of QEMU.
 The ``blacklist`` config file option has been renamed to ``block-rpcs``
 (to be in sync with the renaming of the corresponding command line
 option).
+
+Migration
+---------
+
+``fd:`` URI when used for file migration (since 9.1)
+''''''''''''''''''''''''''''''''''''''''''''''''''''
+
+The ``fd:`` URI can currently provide a file descriptor that
+references either a socket or a plain file. These are two different
+types of migration. In order to reduce ambiguity, the ``fd:`` URI
+usage of providing a file descriptor to a plain file has been
+deprecated in favor of explicitly using the ``file:`` URI with the
+file descriptor being passed as an ``fdset``. Refer to the ``add-fd``
+command documentation for details on the ``fdset`` usage.
-- 
2.35.3



  parent reply	other threads:[~2024-04-25 15:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 15:09 [PATCH 0/6] migration removals & deprecations Fabiano Rosas
2024-04-25 15:09 ` [PATCH 1/6] migration: Remove 'skipped' field from MigrationStats Fabiano Rosas
2024-04-26  5:26   ` Markus Armbruster
2024-04-25 15:09 ` [PATCH 2/6] migration: Remove 'inc' option from migrate command Fabiano Rosas
2024-04-26 13:25   ` Markus Armbruster
2024-04-26 14:07     ` Markus Armbruster
2024-04-25 15:09 ` [PATCH 3/6] migration: Remove 'blk/-b' option from migrate commands Fabiano Rosas
2024-04-26 13:26   ` Markus Armbruster
2024-04-26 14:05     ` Markus Armbruster
2024-04-26 14:19       ` Fabiano Rosas
2024-04-25 15:09 ` [PATCH 4/6] migration: Remove block migration Fabiano Rosas
2024-04-26 14:15   ` Markus Armbruster
2024-04-25 15:09 ` [PATCH 5/6] migration: Remove non-multifd compression Fabiano Rosas
2024-04-26 14:27   ` Markus Armbruster
2024-04-25 15:09 ` Fabiano Rosas [this message]
2024-04-26  6:02 ` [PATCH 0/6] migration removals & deprecations Markus Armbruster
2024-04-26 12:51   ` Fabiano Rosas
2024-04-26 13:08     ` Markus Armbruster
2024-04-26 13:15       ` Fabiano Rosas

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=20240425150939.19268-7-farosas@suse.de \
    --to=farosas@suse.de \
    --cc=berrange@redhat.com \
    --cc=devel@lists.libvirt.org \
    --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).