diff options
| author | Vladimir Sementsov-Ogievskiy | 2022-04-07 15:27:21 +0200 |
|---|---|---|
| committer | Vladimir Sementsov-Ogievskiy | 2022-06-28 09:20:31 +0200 |
| commit | f1bb39a8a5b6d486faa1a51a7f28c577155642c9 (patch) | |
| tree | de0305a84f22213bbff56777df2038c5270dece3 /qapi/error.json | |
| parent | block/copy-before-write: refactor option parsing (diff) | |
| download | qemu-f1bb39a8a5b6d486faa1a51a7f28c577155642c9.tar.gz qemu-f1bb39a8a5b6d486faa1a51a7f28c577155642c9.tar.xz qemu-f1bb39a8a5b6d486faa1a51a7f28c577155642c9.zip | |
block/copy-before-write: add on-cbw-error open parameter
Currently, behavior on copy-before-write operation failure is simple:
report error to the guest.
Let's implement alternative behavior: break the whole copy-before-write
process (and corresponding backup job or NBD client) but keep guest
working. It's needed if we consider guest stability as more important.
The realisation is simple: on copy-before-write failure we set
s->snapshot_ret and continue guest operations. s->snapshot_ret being
set will lead to all further snapshot API requests. Note that all
in-flight snapshot-API requests may still success: we do wait for them
on BREAK_SNAPSHOT-failure path in cbw_do_copy_before_write().
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Diffstat (limited to 'qapi/error.json')
0 files changed, 0 insertions, 0 deletions