From: Steve Sistare <steven.sistare@oracle.com>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Juan Quintela <quintela@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Claudio Fontana <cfontana@suse.de>,
Steve Sistare <steven.sistare@oracle.com>
Subject: [PATCH V5 2/2] migration: file URI offset
Date: Fri, 8 Sep 2023 07:22:11 -0700 [thread overview]
Message-ID: <1694182931-61390-3-git-send-email-steven.sistare@oracle.com> (raw)
In-Reply-To: <1694182931-61390-1-git-send-email-steven.sistare@oracle.com>
Allow an offset option to be specified as part of the file URI, in
the form "file:filename,offset=offset", where offset accepts the common
size suffixes, or the 0x prefix, but not both. Migration data is written
to and read from the file starting at offset. If unspecified, it defaults
to 0.
This is needed by libvirt to store its own data at the head of the file.
Suggested-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
---
migration/file.c | 45 +++++++++++++++++++++++++++++++++++++++++++--
qemu-options.hx | 7 ++++---
2 files changed, 47 insertions(+), 5 deletions(-)
diff --git a/migration/file.c b/migration/file.c
index 0a65c43..cf5b1bf 100644
--- a/migration/file.c
+++ b/migration/file.c
@@ -6,6 +6,8 @@
*/
#include "qemu/osdep.h"
+#include "qemu/cutils.h"
+#include "qapi/error.h"
#include "channel.h"
#include "file.h"
#include "migration.h"
@@ -13,14 +15,41 @@
#include "io/channel-util.h"
#include "trace.h"
-void file_start_outgoing_migration(MigrationState *s, const char *filename,
+#define OFFSET_OPTION ",offset="
+
+/* Remove the offset option from @filespec and return it in @offsetp. */
+
+static int file_parse_offset(char *filespec, uint64_t *offsetp, Error **errp)
+{
+ char *option = strstr(filespec, OFFSET_OPTION);
+ int ret;
+
+ if (option) {
+ *option = 0;
+ option += sizeof(OFFSET_OPTION) - 1;
+ ret = qemu_strtosz(option, NULL, offsetp);
+ if (ret) {
+ error_setg_errno(errp, -ret, "file URI has bad offset %s", option);
+ return -1;
+ }
+ }
+ return 0;
+}
+
+void file_start_outgoing_migration(MigrationState *s, const char *filespec,
Error **errp)
{
+ g_autofree char *filename = g_strdup(filespec);
g_autoptr(QIOChannelFile) fioc = NULL;
+ uint64_t offset = 0;
QIOChannel *ioc;
trace_migration_file_outgoing(filename);
+ if (file_parse_offset(filename, &offset, errp)) {
+ return;
+ }
+
fioc = qio_channel_file_new_path(filename, O_CREAT | O_WRONLY | O_TRUNC,
0600, errp);
if (!fioc) {
@@ -28,6 +57,9 @@ void file_start_outgoing_migration(MigrationState *s, const char *filename,
}
ioc = QIO_CHANNEL(fioc);
+ if (offset && qio_channel_io_seek(ioc, offset, SEEK_SET, errp) < 0) {
+ return;
+ }
qio_channel_set_name(ioc, "migration-file-outgoing");
migration_channel_connect(s, ioc, NULL, NULL);
}
@@ -41,19 +73,28 @@ static gboolean file_accept_incoming_migration(QIOChannel *ioc,
return G_SOURCE_REMOVE;
}
-void file_start_incoming_migration(const char *filename, Error **errp)
+void file_start_incoming_migration(const char *filespec, Error **errp)
{
+ g_autofree char *filename = g_strdup(filespec);
QIOChannelFile *fioc = NULL;
+ uint64_t offset = 0;
QIOChannel *ioc;
trace_migration_file_incoming(filename);
+ if (file_parse_offset(filename, &offset, errp)) {
+ return;
+ }
+
fioc = qio_channel_file_new_path(filename, O_RDONLY, 0, errp);
if (!fioc) {
return;
}
ioc = QIO_CHANNEL(fioc);
+ if (offset && qio_channel_io_seek(ioc, offset, SEEK_SET, errp) < 0) {
+ return;
+ }
qio_channel_set_name(QIO_CHANNEL(ioc), "migration-file-incoming");
qio_channel_add_watch_full(ioc, G_IO_IN,
file_accept_incoming_migration,
diff --git a/qemu-options.hx b/qemu-options.hx
index 54e28c1..2f62672 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -4626,7 +4626,7 @@ DEF("incoming", HAS_ARG, QEMU_OPTION_incoming, \
" prepare for incoming migration, listen on\n" \
" specified protocol and socket address\n" \
"-incoming fd:fd\n" \
- "-incoming file:filename\n" \
+ "-incoming file:filename[,offset=offset]\n" \
"-incoming exec:cmdline\n" \
" accept incoming migration on given file descriptor\n" \
" or from given external command\n" \
@@ -4645,8 +4645,9 @@ SRST
``-incoming fd:fd``
Accept incoming migration from a given file descriptor.
-``-incoming file:filename``
- Accept incoming migration from a given file.
+``-incoming file:filename[,offset=offset]``
+ Accept incoming migration from a given file starting at offset.
+ offset allows the common size suffixes, or a 0x prefix, but not both.
``-incoming exec:cmdline``
Accept incoming migration as an output from specified external
--
1.8.3.1
next prev parent reply other threads:[~2023-09-08 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:22 [PATCH V5 0/2] migration file URI Steve Sistare
2023-09-08 14:22 ` [PATCH V5 1/2] migration: " Steve Sistare
2023-09-08 14:28 ` Daniel P. Berrangé
2023-10-04 11:01 ` Juan Quintela
2023-09-08 14:22 ` Steve Sistare [this message]
2023-09-08 14:27 ` [PATCH V5 2/2] migration: file URI offset Daniel P. Berrangé
2023-10-04 11:17 ` Juan Quintela
2023-09-13 13:05 ` [PATCH V5 0/2] migration file URI Claudio Fontana
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=1694182931-61390-3-git-send-email-steven.sistare@oracle.com \
--to=steven.sistare@oracle.com \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).