Description of problem: the virConnectDomainEventIOErrorReasonCallback API let the client listen for I/O error reasons; the 'reason' value is never populated. Use case: When using the QEMU hypervisor and the disk error policy 'enospc', we need a way to distinguish the actual reason of an I/O error. The 'reason' field is supposed to be such a way. Version-Release number of selected component (if applicable): 1.2.1. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: the 'reason' value is empty Expected results: 'reason' value populated Additional info: Code is explicitely disabled in src/qemu/qemu_monitor_json.c::qemuMonitorJSONHandleIOError
the virDomainGetState API is affected as well, because the I/O error reason reported is the same being populated by the disabled code.
After additional investigation, it seems QEMU doesn not export this information through the QMP protocol. filed a bug against QEMU: https://bugs.launchpad.net/qemu/+bug/1284090
Francesco, http://www.redhat.com/archives/libvir-list/2014-October/msg00129.html is enough, right
(In reply to Michal Skrivanek from comment #4) > Francesco, > http://www.redhat.com/archives/libvir-list/2014-October/msg00129.html is > enough, right Yes, it is sufficient for VDSM use case, but I need to check if virDomainGetState - which VDSM can use in _readPauseCode is fixed as well. If so (as I hope!) we can finally fill this gap.
(In reply to Francesco Romani from comment #5) > (In reply to Michal Skrivanek from comment #4) > > Francesco, > > http://www.redhat.com/archives/libvir-list/2014-October/msg00129.html is > > enough, right > > Yes, it is sufficient for VDSM use case, but I need to check if > virDomainGetState - which VDSM can use in _readPauseCode is fixed as well. > > If so (as I hope!) we can finally fill this gap. Event notification fixed in libvirt 1.2.10. Still checking virDomainGetState
(In reply to Francesco Romani from comment #6) > (In reply to Francesco Romani from comment #5) > > (In reply to Michal Skrivanek from comment #4) > > > Francesco, > > > http://www.redhat.com/archives/libvir-list/2014-October/msg00129.html is > > > enough, right > > > > Yes, it is sufficient for VDSM use case, but I need to check if > > virDomainGetState - which VDSM can use in _readPauseCode is fixed as well. > > > > If so (as I hope!) we can finally fill this gap. > > Event notification fixed in libvirt 1.2.10. Still checking virDomainGetState Covered missing part in https://bugzilla.redhat.com/show_bug.cgi?id=1183086 For events, libvirt >= 1.2.10 is good.
Closing since it sounds like this is fixed