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:
There is one typo in flag description of blkdeviotune man page,
"Both --live and --current flags may be given" should be "Both --live and --config flags may be given".

Version:
libvirt-1.2.8-5.el7.x86_64

How reproducible:
100%

Steps to Reproduce:

1.
#man virsh

 blkdeviotune domain device [[--config] [--live] | [--current]] [[total-bytes-sec] | [read-bytes-sec] [write-bytes-sec]]
       [[total-iops-sec] | [read-iops-sec] [write-iops-sec]]
.........

 Both --live and --current flags may be given, but --current
           is exclusive. If no flag is specified, behavior is different depending on hypervisor.

2.
check another command like 'blkiotune':

 Both --live and --config flags may be given, but --current
           is exclusive. If no flag is specified, behavior is different depending on hypervisor.


Actual results:
In step 1, the "Both --live and --current flags may be given" is wrong,

Expected results:
In step 1, it should be "Both --live and --config flags may be given" like which one in step 2.

Fixed upstream:

commit 59de544f6a1a8d022a15993c9bd026b0c3a12f22
Author: Peter Krempa <pkrempa>
Date:   Tue Oct 14 09:41:24 2014 +0200

    virsh: man: Fix description of --live/--config usage
    
    dommemstat and blkdeviotune's man page incorrectly stated the usage of
    --live and --config.

Verified, 
Versions:
# rpm -qa | grep libvirt-1
libvirt-1.2.13-1.el7.x86_64


steps:
1. man virsh
2. search /blkdeviotune
3. check the modified doc segment. As follow: 
If --live is specified, affect a running guest.  If --config is specified, affect the next boot of a persistent guest.  If --current is
           specified, affect the current guest state.  When setting the disk io parameters both --live and --config flags may be given, but
           --current is exclusive. For querying only one of --live, --config or --current can be specified. If no flag is specified, behavior is
           different depending on hypervisor.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2202.html