From: Fabiano Rosas <farosas@suse.de>
To: Roman Khapov <rkhapov@yandex-team.ru>, qemu-devel@nongnu.org
Cc: peterx@redhat.com, eblake@redhat.com, armbru@redhat.com,
yc-core@yandex-team.ru, Roman Khapov <rkhapov@yandex-team.ru>
Subject: Re: [PATCH v2 0/2] Field 'reason' for MIGRATION event
Date: Wed, 21 Feb 2024 11:45:42 -0300 [thread overview]
Message-ID: <87jzmxc1ux.fsf@suse.de> (raw)
In-Reply-To: <20240215122759.1438581-1-rkhapov@yandex-team.ru>
Roman Khapov <rkhapov@yandex-team.ru> writes:
Hi Roman,
> This is resending of series 20240215082659.1378342-1-rkhapov@yandex-team.ru,
> where patch subjects numbers were broken in patch 2/2.
>
> Sometimes, when migration fails, it is hard to find out
> the cause of the problems: you have to grep qemu logs.
> At the same time, there is MIGRATION event, which looks like
> suitable place to hold such error descriptions.
query-migrate after the event is received should be enough for giving
you the failure reason. We have that in error-desc. See commit
c94143e587 ("migration: Display error in query-migrate irrelevant of
status").
>
> To handle situation like this (maybe one day it will be useful
> for other MIGRATION statuses to have additional 'reason' strings),
I find it unlikely. There's no "reason" for making progress except
that's how things work. Only the exceptional (i.e. failure) statuses
would have a reason. Today that's FAILED only, maybe also
POSTCOPY_PAUSED.
> the general optional field 'reason' can be added.
>
> The series proposes next changes:
>
> 1. Adding optional 'reason' field of type str into
> qapi/migration.json MIGRATION event
>
> 2. Passing some error description as reason for every place, which
> sets migration state to MIGRATION_STATUS_FAILED
>
> After the series, MIGRATION event will looks like this:
> {"execute": "qmp_capabilities"}
> {"return": {}}
> {"event": "MIGRATION", "data": {"status": "setup"}}
> {"event": "MIGRATION", "data": {"status": "failed", "reason": "Failed to connect to '/tmp/sock.sock': No such file or directory"}}
>
> Roman Khapov (2):
> qapi/migration.json: add reason to MIGRATION event
> migration: add error reason for failed MIGRATION events
>
> migration/colo.c | 6 +-
> migration/migration.c | 128 ++++++++++++++++++++++++++++--------------
> migration/migration.h | 5 +-
> migration/multifd.c | 10 ++--
> migration/savevm.c | 24 ++++----
> qapi/migration.json | 3 +-
> 6 files changed, 112 insertions(+), 64 deletions(-)
Please remember to run make check:
380/383 qemu:qtest+qtest-x86_64 / qtest-x86_64/migration-test ERROR
104.77s killed by signal 6 SIGABRT
―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stderr: Broken pipe ../tests/qtest/libqtest.c:204: kill_qemu() detected
QEMU death from signal 11 (Segmentation fault) (core dumped)
Most likely one of the new error_setg has broken postcopy recovery. Some
of those paths are not intended to trigger cleanup.
next prev parent reply other threads:[~2024-02-21 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 12:27 [PATCH v2 0/2] Field 'reason' for MIGRATION event Roman Khapov
2024-02-15 12:27 ` [PATCH v2 1/2] qapi/migration.json: add reason to " Roman Khapov
2024-02-16 6:17 ` Markus Armbruster
2024-02-18 14:32 ` Roman Khapov
2024-02-19 6:35 ` Markus Armbruster
2024-02-21 13:36 ` Roman Khapov
2024-02-20 5:39 ` Peter Xu
2024-02-21 13:47 ` Roman Khapov
2024-02-22 9:22 ` Peter Xu
2024-02-15 12:27 ` [PATCH v2 2/2] migration: add error reason for failed MIGRATION events Roman Khapov
2024-02-21 14:45 ` Fabiano Rosas [this message]
2024-02-22 7:01 ` [PATCH v2 0/2] Field 'reason' for MIGRATION event Markus Armbruster
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=87jzmxc1ux.fsf@suse.de \
--to=farosas@suse.de \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkhapov@yandex-team.ru \
--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;
as well as URLs for NNTP newsgroup(s).