Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
------------------------
as subject, "value" should be "speed":
block-job-set-speed
--------------------
Set maximum speed for a background block operation.
This command can only be issued when there is an active block job.
Throttling can be disabled by setting the speed to 0.
Arguments:
- device: the device name
- value: the maximum speed, in bytes per second
Returns:
Nothing on success
If the job type does not support throttling, NotSupported
If streaming is not active on this device, DeviceNotActive
Example:
-> { "execute": "block-job-set-speed",
"arguments": { "device": "virtio0", "value": 1024 } }
Version-Release number of selected component (if applicable):
--------------------------------------------------------------
qemu-kvm-rhev-295
Comment 1RHEL Program Management
2012-07-10 08:14:14 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2RHEL Program Management
2012-07-11 02:08:24 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Description of problem: ------------------------ as subject, "value" should be "speed": block-job-set-speed -------------------- Set maximum speed for a background block operation. This command can only be issued when there is an active block job. Throttling can be disabled by setting the speed to 0. Arguments: - device: the device name - value: the maximum speed, in bytes per second Returns: Nothing on success If the job type does not support throttling, NotSupported If streaming is not active on this device, DeviceNotActive Example: -> { "execute": "block-job-set-speed", "arguments": { "device": "virtio0", "value": 1024 } } Version-Release number of selected component (if applicable): -------------------------------------------------------------- qemu-kvm-rhev-295