diff options
Diffstat (limited to 'mailinglist/output_launchpad/1349722')
| -rw-r--r-- | mailinglist/output_launchpad/1349722 | 47 |
1 files changed, 47 insertions, 0 deletions
diff --git a/mailinglist/output_launchpad/1349722 b/mailinglist/output_launchpad/1349722 new file mode 100644 index 00000000..64eb0fdd --- /dev/null +++ b/mailinglist/output_launchpad/1349722 @@ -0,0 +1,47 @@ +qemu-io: Exit code is always zero + +The qemu-io always returns zero on exit independently on errors occurred during the command execution. + +Example, + +$ qemu-io -c 'write 128 234' /tmp/run1/test-1/test.img + +offset 128 is not sector aligned + +$ echo $? +0 + + +qemu.git HEAD: 41a1a9c42c4e + +On Tue, Jul 29, 2014 at 08:07:44AM -0000, Maria Kustova wrote: +> The qemu-io always returns zero on exit independently on errors occurred +> during the command execution. +> +> Example, +> +> $ qemu-io -c 'write 128 234' /tmp/run1/test-1/test.img +> +> offset 128 is not sector aligned +> +> $ echo $? +> 0 +> +> +> qemu.git HEAD: 41a1a9c42c4e + +For single commands it makes sense to return the command success as the +exit code. + +When qemu-io is used interactively or with multiple -c options we need a +error handling policy. + +For this reason it is not totally trivial to implement. + +Stefan + + +Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays? + +Should be fixed as of 6b3aa8485ca8e. + |