[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 5/6] migration: Rephrase message on failure to save / load Xe
From: |
Peter Xu |
Subject: |
Re: [PATCH 5/6] migration: Rephrase message on failure to save / load Xen device state |
Date: |
Thu, 23 May 2024 15:43:32 -0400 |
On Mon, May 13, 2024 at 04:17:02PM +0200, Markus Armbruster wrote:
> Functions that use an Error **errp parameter to return errors should
> not also report them to the user, because reporting is the caller's
> job. When the caller does, the error is reported twice. When it
> doesn't (because it recovered from the error), there is no error to
> report, i.e. the report is bogus.
>
> qmp_xen_save_devices_state() and qmp_xen_load_devices_state() violate
> this principle: they call qemu_save_device_state() and
> qemu_loadvm_state(), which call error_report_err().
>
> I wish I could clean this up now, but migration's error reporting is
> too complicated (confused?) for me to mess with it.
:-(
>
> Instead, I'm merely improving the error reported by
> qmp_xen_load_devices_state() and qmp_xen_load_devices_state() to the
> QMP core from
>
> An IO error has occurred
>
> to
> saving Xen device state failed
>
> and
>
> loading Xen device state failed
>
> respectively.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
- Re: [PATCH 2/6] dump/win_dump: Improve error messages on write error, (continued)
[PATCH 6/6] qerror: QERR_IO_ERROR is no longer used, drop, Markus Armbruster, 2024/05/13
[PATCH 3/6] block/vmdk: Improve error messages on extent write error, Markus Armbruster, 2024/05/13
[PATCH 5/6] migration: Rephrase message on failure to save / load Xen device state, Markus Armbruster, 2024/05/13
[PATCH 1/6] block: Improve error message when external snapshot can't flush, Markus Armbruster, 2024/05/13
[PATCH 4/6] cpus: Improve error messages on memsave, pmemsave write error, Markus Armbruster, 2024/05/13