Comment 8Markus Armbruster
2018-08-09 08:10:07 UTC
Error checking and reporting for -kernel, -initrd etc. is as poor as ever. Here's an example with current upstream:
$ qemu-system-x86_64 -nodefaults -S -display none -kernel /dev/null
qemu: could not load kernel '/dev/null': No such file or directory
The "No such file or directory" is bogus.
A reasonably complete fix shouldn't be technically challenging, just tedious work (the bugs are both in generic and machine-specific code).
(In reply to Markus Armbruster from comment #8)
> Error checking and reporting for -kernel, -initrd etc. is as poor as ever.
> Here's an example with current upstream:
>
> $ qemu-system-x86_64 -nodefaults -S -display none -kernel /dev/null
> qemu: could not load kernel '/dev/null': No such file or directory
>
> The "No such file or directory" is bogus.
>
> A reasonably complete fix shouldn't be technically challenging, just tedious
> work (the bugs are both in generic and machine-specific code).
These are corner-cases we typically don't support anyway (customers don't hit them using libvirt). I'm closing it as WONTFIX. If there are specific use-cases that customers might hit, then please report them.