If the qcow initialization fails after we created the storage file, we should remove it to avoid leaving stale files around.
We already do this for luks raw images. Signed-off-by: Maxim Levitsky <mlevi...@redhat.com> --- block/qcow2.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/block/qcow2.c b/block/qcow2.c index b05512718c..4dc6102df8 100644 --- a/block/qcow2.c +++ b/block/qcow2.c @@ -3834,6 +3834,18 @@ static int coroutine_fn qcow2_co_create_opts(BlockDriver *drv, /* Create the qcow2 image (format layer) */ ret = qcow2_co_create(create_options, errp); if (ret < 0) { + + Error *local_delete_err = NULL; + int r_del = bdrv_co_delete_file(bs, &local_delete_err); + /* + * ENOTSUP will happen if the block driver doesn't support + * the 'bdrv_co_delete_file' interface. This is a predictable + * scenario and shouldn't be reported back to the user. + */ + if ((r_del < 0) && (r_del != -ENOTSUP)) { + error_report_err(local_delete_err); + } + error_free(local_delete_err); goto finish; } -- 2.26.2