From: "Michael S. Tsirkin" <mst@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/5] Exit if incoming migration fails
Date: Mon, 24 May 2010 14:53:42 +0300 [thread overview]
Message-ID: <20100524115342.GA2089@redhat.com> (raw)
In-Reply-To: <9fed8fc8d5a596bd8fdf125ffadc8f55dc39eb2b.1274688090.git.quintela@redhat.com>
On Mon, May 24, 2010 at 10:25:25AM +0200, Juan Quintela wrote:
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> ---
> migration.c | 14 +++++++-------
> migration.h | 2 +-
> vl.c | 5 ++++-
> 3 files changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/migration.c b/migration.c
> index 05f6cc5..cf30a8e 100644
> --- a/migration.c
> +++ b/migration.c
> @@ -36,22 +36,22 @@ static uint32_t max_throttle = (32 << 20);
>
> static MigrationState *current_migration;
>
> -void qemu_start_incoming_migration(const char *uri)
> +int qemu_start_incoming_migration(const char *uri)
> {
> const char *p;
> + int ret = -1;
>
> if (strstart(uri, "tcp:", &p))
> - tcp_start_incoming_migration(p);
> + ret = tcp_start_incoming_migration(p);
> #if !defined(WIN32)
> else if (strstart(uri, "exec:", &p))
> - exec_start_incoming_migration(p);
> + ret = exec_start_incoming_migration(p);
> else if (strstart(uri, "unix:", &p))
> - unix_start_incoming_migration(p);
> + ret = unix_start_incoming_migration(p);
> else if (strstart(uri, "fd:", &p))
> - fd_start_incoming_migration(p);
> + ret = fd_start_incoming_migration(p);
> #endif
> - else
> - fprintf(stderr, "unknown migration protocol: %s\n", uri);
I think we need this message, this is where we know
reason for failure is bad protocol.
> + return ret;
> }
>
> int do_migrate(Monitor *mon, const QDict *qdict, QObject **ret_data)
> diff --git a/migration.h b/migration.h
> index 385423f..dd423a1 100644
> --- a/migration.h
> +++ b/migration.h
> @@ -50,7 +50,7 @@ struct FdMigrationState
> void *opaque;
> };
>
> -void qemu_start_incoming_migration(const char *uri);
> +int qemu_start_incoming_migration(const char *uri);
>
> int do_migrate(Monitor *mon, const QDict *qdict, QObject **ret_data);
>
> diff --git a/vl.c b/vl.c
> index d77b47c..3dfab9e 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -3841,7 +3841,10 @@ int main(int argc, char **argv, char **envp)
> }
>
> if (incoming) {
> - qemu_start_incoming_migration(incoming);
> + if (qemu_start_incoming_migration(incoming) < 0) {
> + fprintf(stderr, "unknown migration protocol: %s\n", incoming);
> + exit(1);
> + }
Let's put here: 'Migration failed. Exit code %s(%d), exiting.\n'
and then exit(ret);
> } else if (autostart) {
> vm_start();
> }
> --
> 1.6.6.1
>
next prev parent reply other threads:[~2010-05-24 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 8:25 [Qemu-devel] [PATCH 0/5] Add QMP migration events Juan Quintela
2010-05-24 8:25 ` [Qemu-devel] [PATCH 1/5] Exit if incoming migration fails Juan Quintela
2010-05-24 9:02 ` [Qemu-devel] " Paolo Bonzini
2010-05-24 11:53 ` Michael S. Tsirkin [this message]
2010-05-24 8:25 ` [Qemu-devel] [PATCH 2/5] Factorize common migration incoming code Juan Quintela
2010-05-24 8:25 ` [Qemu-devel] [PATCH 3/5] QMP: Introduce MIGRATION events Juan Quintela
2010-05-24 9:04 ` [Qemu-devel] " Paolo Bonzini
2010-05-24 8:25 ` [Qemu-devel] [PATCH 4/5] QMP: Emit migration events on incoming migration Juan Quintela
2010-05-24 8:25 ` [Qemu-devel] [PATCH 5/5] QMP: Emit migration events on outgoing migration Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2010-05-25 14:21 [Qemu-devel] [PATCH v2 0/5] Add QMP migration events Juan Quintela
2010-05-25 14:21 ` [Qemu-devel] [PATCH 1/5] Exit if incoming migration fails Juan Quintela
2010-05-25 18:01 ` Luiz Capitulino
2010-05-25 18:37 ` [Qemu-devel] " Juan Quintela
2010-05-25 18:52 ` Anthony Liguori
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=20100524115342.GA2089@redhat.com \
--to=mst@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).