Goal

When debugging storage related issues the reason for a I/O may contain important information leading to the root cause. QEMU itself reports the error reason, but libvirt and CNV don't expose it. The error itself is thus deeply buried only in debug logs of libvirtd.

The goal of this issue is to improve the error propagation to upper layers so that the errors can be captured in more visible and easier to access logs.

Background

It is a recurring pattern that customers report I/O errors, but the logs don't show the full information that QEMU knows. Most recently, in the Portwork case at https://access.redhat.com/support/cases/#/case/04024671 there were logs available that showed that there was an I/O error, but not what error occurred. If we had been able to tell directly from the logs that it was "Invalid argument", that might have allowed us to find the solution earlier.

Acceptance criteria

A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.

• Improve logging of I/O errors to include the reason string that QEMU exposes

Additional information

Please refer to RHEL-76802 for the libvirt interfaces that expose the reason to upper layers.