- Original Message -
> From: "Eric Blake"
> To: "Francesco Romani"
> Cc: libvir-l...@redhat.com, "Nir Soffer" , "Peter Krempa"
> ,
> qemu-devel@nongnu.org
> Sent: Friday, May 22, 2015 6:33:01 AM
> Subject: Re: [libvirt] RFC
patch posted on qemu-devel, reviewd, acked and merged into maintainer's branch:
https://github.com/stefanha/qemu/commit/f050ea639522e9dd7e501ef285a2a12709b8726a
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
- Original Message -
> From: "Stefan Hajnoczi"
> To: "Francesco Romani"
> Cc: qemu-devel@nongnu.org, kw...@redhat.com, lcapitul...@redhat.com,
> mdr...@linux.vnet.ibm.com, ebl...@redhat.com
> Sent: Tuesday, January 13, 2015 2:54:41 PM
> Subject: Re:
hold' field into the `BlockDeviceInfo' structure,
to report the configured threshold.
This will allow the managing application to use smarter and more
efficient monitoring, greatly reducing the need of polling.
Signed-off-by: Francesco Romani
Reviewed-by: Eric Blake
---
block/M
Hi,
thanks for the review!
- Original Message -
> From: "Eric Blake"
> To: "Francesco Romani" , qemu-devel@nongnu.org
> Cc: kw...@redhat.com, mdr...@linux.vnet.ibm.com, stefa...@redhat.com,
> lcapitul...@redhat.com
> Sent: Friday, January 9, 2015 5:
ping
- Original Message -
> From: "Francesco Romani"
> To: qemu-devel@nongnu.org
> Cc: kw...@redhat.com, mdr...@linux.vnet.ibm.com, stefa...@redhat.com,
> lcapitul...@redhat.com
> Sent: Monday, December 15, 2014 12:19:44 PM
> Subject: Re: [Qemu-devel] [PAT
ping?
- Original Message -
> From: "Francesco Romani"
> To: qemu-devel@nongnu.org
> Cc: kw...@redhat.com, mdr...@linux.vnet.ibm.com, stefa...@redhat.com,
> lcapitul...@redhat.com
> Sent: Thursday, December 4, 2014 10:00:18 AM
> Subject: Re: [Qemu-devel] [PAT
- Original Message -
> From: "Francesco Romani"
> To: qemu-devel@nongnu.org
> Cc: kw...@redhat.com, stefa...@redhat.com, lcapitul...@redhat.com,
> mdr...@linux.vnet.ibm.com, ebl...@redhat.com,
> "Francesco Romani"
> Sent: Thursday, December 4, 2014
monitoring, greatly reducing the need of polling.
A followup patch is planned to allow to add the write threshold at
device creation.
Signed-off-by: Francesco Romani
---
block/Makefile.objs | 1 +
block/qapi.c| 3 +
block/write-threshold.c
- Original Message -
> From: "Stefan Hajnoczi"
> To: "Francesco Romani"
> Cc: kw...@redhat.com, mdr...@linux.vnet.ibm.com, qemu-devel@nongnu.org,
> lcapitul...@redhat.com
> Sent: Tuesday, December 2, 2014 4:01:17 PM
> Subject: Re: [Qemu-devel
- Original Message -
> From: "Francesco Romani"
> To: "Eric Blake"
> Cc: kw...@redhat.com, lcapitul...@redhat.com, qemu-devel@nongnu.org,
> stefa...@redhat.com, mdr...@linux.vnet.ibm.com
> Sent: Tuesday, December 2, 2014 8:47:45 AM
> Subject: Re: [
Thanks for the quick review!
- Original Message -
> From: "Eric Blake"
> To: "Francesco Romani" , qemu-devel@nongnu.org
> Cc: kw...@redhat.com, mdr...@linux.vnet.ibm.com, stefa...@redhat.com,
> lcapitul...@redhat.com
> Sent: Monday, December 1, 20
rces
and come up with this tentative patch which I'd also like
to submit.
Notes
-
[0]: https://lists.gnu.org/archive/html/qemu-devel/2014-07/msg01348.html
[1]:
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=ebb0c19c48690f0598de954f8e0e9d4d29d48b85
Francesco Romani (1):
blo
wait for a watermark crossing event.
Signed-off-by: Francesco Romani
---
block/Makefile.objs | 1 +
block/qapi.c| 3 +
block/usage-threshold.c | 124
include/block/block_int.h | 4 ++
include/block/usage-thresho
- Original Message -
> From: "Kevin Wolf"
> To: "Francesco Romani"
> Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" ,
> mdr...@linux.vnet.ibm.com, "Luiz Capitulino"
> , "Stefan Hajnoczi"
> Sent: Friday, November 21, 201
- Original Message -
> From: "Kevin Wolf"
> To: "Stefan Hajnoczi"
> Cc: mdr...@linux.vnet.ibm.com, "Stefan Hajnoczi" ,
> lcapitul...@redhat.com, qemu-devel@nongnu.org,
> "Francesco Romani"
> Sent: Thursday, November 20, 2014 12:
- Original Message -
> From: "Stefan Hajnoczi"
> To: "Francesco Romani"
> Cc: kw...@redhat.com, "Stefan Hajnoczi" ,
> mdr...@linux.vnet.ibm.com, qemu-devel@nongnu.org,
> lcapitul...@redhat.com
> Sent: Wednesday, November 19, 2014 4:52:
- Original Message -
> From: "Stefan Hajnoczi"
> To: "Francesco Romani"
> Cc: kw...@redhat.com, lcapitul...@redhat.com, qemu-devel@nongnu.org,
> stefa...@redhat.com, mdr...@linux.vnet.ibm.com
> Sent: Monday, November 17, 2014 5:49:36 PM
> Subject:
wait for a watermark crossing event.
Signed-off-by: Francesco Romani
---
block/Makefile.objs | 1 +
block/qapi.c| 3 +
block/usage-threshold.c | 124
include/block/block_int.h | 4 ++
include/block/usage-thresho
I had the chance to take a look at the QEMU sources
and come up with this tentative patch which I'd also like
to submit.
Notes
-
[0]: https://lists.gnu.org/archive/html/qemu-devel/2014-07/msg01348.html
[1]:
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=ebb0c19c48690f0598de9
- Original Message -
> From: "Stefan Hajnoczi"
> To: "Kevin Wolf"
> Cc: mdr...@linux.vnet.ibm.com, "Francesco Romani" ,
> qemu-devel@nongnu.org, lcapitul...@redhat.com
> Sent: Tuesday, August 5, 2014 3:08:46 PM
> Subject: Re: [Qemu-devel
Sorry, this is actually an RFC; patch was posted separately.
- Original Message -
> From: "Francesco Romani"
> To: qemu-devel@nongnu.org
> Cc: kw...@redhat.com, stefa...@redhat.com, lcapitul...@redhat.com,
> mdr...@linux.vnet.ibm.com, "Francesco Romani"
just wait for a watermark crossing event.
Signed-off-by: Francesco Romani
---
block.c | 56 +++
blockdev.c| 21 ++
include/block/block.h | 2 ++
include/block/block_int.h | 3 +++
qapi/block-core.json
imit is crossed.
To track this RFE I filed https://bugs.launchpad.net/qemu/+bug/1338957
Moreover, I had the chance to take a look at the QEMU sources
and come up with this tentative patch which I'd also like
to submit.
Comments and thoughts very welcome!
Thanks and best regards,
Francesco
Public bug reported:
Add an event to report if a block device usage exceeds a threshold. The
threshold should be configurable with a monitor command. The event
should report the affected block device. Additional useful information
could be the offset of the highest sector , like in the query-block
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 p
26 matches
Mail list logo
