RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.