qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [Bug 1284090] [NEW] RFE: QMP: report error reason in BLOCK_IO_ERROR message
@ 2014-02-24 12:32 Francesco Romani
  2017-04-27 15:32 ` [Qemu-devel] [Bug 1284090] " Thomas Huth
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Francesco Romani @ 2014-02-24 12:32 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

when a disk drive is configured with the error policy enospc for write errors, the monitoring client needs a way to distinguish
betwwen generic I/O error and the I/O error for space exausted.

The JSON QMP protocol lacks this information: the BLOCK_IO_ERROR message
does not provide a reason or code for the error verified, so the
monitoring client cannot distinguish the source of the errors.

verified against git 105a060188dc6fdd4551571a966514d1a5f6815a

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1284090

Title:
  RFE: QMP: report error reason in BLOCK_IO_ERROR message

Status in QEMU:
  New

Bug description:
  when a disk drive is configured with the error policy enospc for write errors, the monitoring client needs a way to distinguish
  betwwen generic I/O error and the I/O error for space exausted.

  The JSON QMP protocol lacks this information: the BLOCK_IO_ERROR
  message does not provide a reason or code for the error verified, so
  the monitoring client cannot distinguish the source of the errors.

  verified against git 105a060188dc6fdd4551571a966514d1a5f6815a

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1284090/+subscriptions

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Qemu-devel] [Bug 1284090] Re: RFE: QMP: report error reason in BLOCK_IO_ERROR message
  2014-02-24 12:32 [Qemu-devel] [Bug 1284090] [NEW] RFE: QMP: report error reason in BLOCK_IO_ERROR message Francesco Romani
@ 2017-04-27 15:32 ` Thomas Huth
  2020-11-20 18:37 ` Thomas Huth
  2021-01-20  4:17 ` Launchpad Bug Tracker
  2 siblings, 0 replies; 4+ messages in thread
From: Thomas Huth @ 2017-04-27 15:32 UTC (permalink / raw)
  To: qemu-devel

** Changed in: qemu
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1284090

Title:
  RFE: QMP: report error reason in BLOCK_IO_ERROR message

Status in QEMU:
  New

Bug description:
  when a disk drive is configured with the error policy enospc for write errors, the monitoring client needs a way to distinguish
  betwwen generic I/O error and the I/O error for space exausted.

  The JSON QMP protocol lacks this information: the BLOCK_IO_ERROR
  message does not provide a reason or code for the error verified, so
  the monitoring client cannot distinguish the source of the errors.

  verified against git 105a060188dc6fdd4551571a966514d1a5f6815a

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1284090/+subscriptions

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug 1284090] Re: RFE: QMP: report error reason in BLOCK_IO_ERROR message
  2014-02-24 12:32 [Qemu-devel] [Bug 1284090] [NEW] RFE: QMP: report error reason in BLOCK_IO_ERROR message Francesco Romani
  2017-04-27 15:32 ` [Qemu-devel] [Bug 1284090] " Thomas Huth
@ 2020-11-20 18:37 ` Thomas Huth
  2021-01-20  4:17 ` Launchpad Bug Tracker
  2 siblings, 0 replies; 4+ messages in thread
From: Thomas Huth @ 2020-11-20 18:37 UTC (permalink / raw)
  To: qemu-devel

The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.

** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1284090

Title:
  RFE: QMP: report error reason in BLOCK_IO_ERROR message

Status in QEMU:
  Incomplete

Bug description:
  when a disk drive is configured with the error policy enospc for write errors, the monitoring client needs a way to distinguish
  betwwen generic I/O error and the I/O error for space exausted.

  The JSON QMP protocol lacks this information: the BLOCK_IO_ERROR
  message does not provide a reason or code for the error verified, so
  the monitoring client cannot distinguish the source of the errors.

  verified against git 105a060188dc6fdd4551571a966514d1a5f6815a

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1284090/+subscriptions


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug 1284090] Re: RFE: QMP: report error reason in BLOCK_IO_ERROR message
  2014-02-24 12:32 [Qemu-devel] [Bug 1284090] [NEW] RFE: QMP: report error reason in BLOCK_IO_ERROR message Francesco Romani
  2017-04-27 15:32 ` [Qemu-devel] [Bug 1284090] " Thomas Huth
  2020-11-20 18:37 ` Thomas Huth
@ 2021-01-20  4:17 ` Launchpad Bug Tracker
  2 siblings, 0 replies; 4+ messages in thread
From: Launchpad Bug Tracker @ 2021-01-20  4:17 UTC (permalink / raw)
  To: qemu-devel

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1284090

Title:
  RFE: QMP: report error reason in BLOCK_IO_ERROR message

Status in QEMU:
  Expired

Bug description:
  when a disk drive is configured with the error policy enospc for write errors, the monitoring client needs a way to distinguish
  betwwen generic I/O error and the I/O error for space exausted.

  The JSON QMP protocol lacks this information: the BLOCK_IO_ERROR
  message does not provide a reason or code for the error verified, so
  the monitoring client cannot distinguish the source of the errors.

  verified against git 105a060188dc6fdd4551571a966514d1a5f6815a

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1284090/+subscriptions


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-01-20  4:31 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-24 12:32 [Qemu-devel] [Bug 1284090] [NEW] RFE: QMP: report error reason in BLOCK_IO_ERROR message Francesco Romani
2017-04-27 15:32 ` [Qemu-devel] [Bug 1284090] " Thomas Huth
2020-11-20 18:37 ` Thomas Huth
2021-01-20  4:17 ` Launchpad Bug Tracker

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).