block: Be more verbose in create fallback
PATCH 1/1 block: Be more verbose in create fallback
For image creation code, we have central fallback code for protocols that do not support creating new images (like NBD or iscsi). So for them, you can only specify existing paths/exports that are overwritten to make clean new images. In such a case, if the given path cannot be opened (assuming a pre-existing image there), we print an error message that tries to describe what is going on: That with this protocol, you cannot create new images, but only overwrite existing ones; and the given path could not be opened as a pre-existing image.
However, the current message is confusing, because it does not say that the protocol in question does not support creating new images, but instead that "image creation" is unsupported. This can be interpreted to mean that qemu-img create will not work in principle, which is not true. Be more verbose for clarity.
--- block.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
block.c +4 -2
@@ -661,8 +661,10 @@ int coroutine_fn bdrv_co_create_opts_simple(BlockDriver *drv, blk =blk_co_new_open (filename,NULL , options,BDRV_O_RDWR |BDRV_O_RESIZE , errp);if (!blk) { -error_prepend (errp,"Protocol driver '%s' does not support image " -"creation, and opening the image failed: " , +error_prepend (errp,"Protocol driver '%s' does not support creating " +"new images, so an existing image must be selected as " +"the target; however, opening the given target as an " +"existing image failed: " , drv->format_name);return -EINVAL ; }
Signature · 1 line
2.41.0
Quoted 15 lines · Hanna Czenczek
For image creation code, we have central fallback code for protocols that do not support creating new images (like NBD or iscsi). So for them, you can only specify existing paths/exports that are overwritten to make clean new images. In such a case, if the given path cannot be opened (assuming a pre-existing image there), we print an error message that tries to describe what is going on: That with this protocol, you cannot create new images, but only overwrite existing ones; and the given path could not be opened as a pre-existing image.
However, the current message is confusing, because it does not say that the protocol in question does not support creating new images, but instead that "image creation" is unsupported. This can be interpreted to mean that
qemu-img createwill not work in principle, which is not true. Be more verbose for clarity.
Quoted 5 lines
Signed-off-by Hanna Czenczek <[email protected]>--- block.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
Definitely more vebose, but I don't see that as a bad thing.
Quoted 22 lines
block.c +4
-2@@ -661,8 +661,10 @@ int coroutine_fn bdrv_co_create_opts_simple(BlockDriver *drv, blk =blk_co_new_open (filename,NULL , options,BDRV_O_RDWR |BDRV_O_RESIZE , errp);if (!blk) { -error_prepend (errp,"Protocol driver '%s' does not support image " -"creation, and opening the image failed: " , +error_prepend (errp,"Protocol driver '%s' does not support creating " +"new images, so an existing image must be selected as " +"the target; however, opening the given target as an " +"existing image failed: " , drv->format_name);return -EINVAL ; }Signature · 1 line
2.41.0
Signature · 3 lines
Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
Kevin Wolf
AppliedAm 20.07.2023 um 16:00 hat Hanna Czenczek geschrieben:
Quoted 9 lines
For image creation code, we have central fallback code for protocols that do not support creating new images (like NBD or iscsi). So for them, you can only specify existing paths/exports that are overwritten to make clean new images. In such a case, if the given path cannot be opened (assuming a pre-existing image there), we print an error message that tries to describe what is going on: That with this protocol, you cannot create new images, but only overwrite existing ones; and the given path could not be opened as a pre-existing image.
Quoted 8 lines
However, the current message is confusing, because it does not say that the protocol in question does not support creating new images, but instead that "image creation" is unsupported. This can be interpreted to mean that
qemu-img createwill not work in principle, which is not true. Be more verbose for clarity.Signed-off-by Hanna Czenczek <[email protected]>
Thanks, applied to the block branch.
Kevin