[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1338957] [NEW] RFE: add an event to report block devic
From: |
Francesco Romani |
Subject: |
[Qemu-devel] [Bug 1338957] [NEW] RFE: add an event to report block devices watermark |
Date: |
Tue, 08 Jul 2014 09:12:08 -0000 |
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-blockstats
output.
Rationale for the RFE
Managing applications, like oVirt (http://www.ovirt.org), make extensive use of
thin-provisioned disk images.
In order to let the guest run flawlessly and be not unnecessarily paused, oVirt
sets a watermark and automatically resized the image once the watermark is
reached or exceeded.
In order to detect the mark crossing, the managing application has no choice
than aggressively polling the QEMU monitor
using the query-blockstats command. This lead to unnecessary system load, and
is made even worse under scale: scenarios
with hunderds of VM are becoming not unusual.
** 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/1338957
Title:
RFE: add an event to report block devices watermark
Status in QEMU:
New
Bug description:
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-
blockstats output.
Rationale for the RFE
Managing applications, like oVirt (http://www.ovirt.org), make extensive use
of thin-provisioned disk images.
In order to let the guest run flawlessly and be not unnecessarily paused,
oVirt sets a watermark and automatically resized the image once the watermark
is reached or exceeded.
In order to detect the mark crossing, the managing application has no choice
than aggressively polling the QEMU monitor
using the query-blockstats command. This lead to unnecessary system load, and
is made even worse under scale: scenarios
with hunderds of VM are becoming not unusual.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1338957/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |