On Tue, Apr 24, 2012 at 8:14 PM, Luiz Capitulino lcapitul...@redhat.com wrote:
# Returns: Nothing on success
# If streaming is already active on this device, DeviceInUse
# If @device does not exist, DeviceNotFound
# If image streaming is not supported by this
Am 24.04.2012 15:53, schrieb Stefan Hajnoczi:
diff --git a/qapi-schema.json b/qapi-schema.json
index d56fcb6..b1e349f 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -1571,15 +1571,19 @@
#
# @base: #optional the common backing file name
#
+# @speed: #optional the maximum
Allow streaming operations to be started with an initial speed limit.
This eliminates the window of time between starting streaming and
issuing block-job-set-speed. Users should use the new optional 'speed'
parameter instead so that speed limits are in effect immediately when
the job starts.
On Tue, Apr 24, 2012 at 4:17 PM, Eric Blake ebl...@redhat.com wrote:
On 04/24/2012 07:53 AM, Stefan Hajnoczi wrote:
Allow streaming operations to be started with an initial speed limit.
This eliminates the window of time between starting streaming and
issuing block-job-set-speed. Users should
On 04/24/2012 07:53 AM, Stefan Hajnoczi wrote:
Allow streaming operations to be started with an initial speed limit.
This eliminates the window of time between starting streaming and
issuing block-job-set-speed. Users should use the new optional 'speed'
parameter instead so that speed limits
On Tue, 24 Apr 2012 14:53:58 +0100
Stefan Hajnoczi stefa...@linux.vnet.ibm.com wrote:
Allow streaming operations to be started with an initial speed limit.
This eliminates the window of time between starting streaming and
issuing block-job-set-speed. Users should use the new optional 'speed'
