---
tools/virsh.pod | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/virsh.pod b/tools/virsh.pod
index f8496f3..f576fb0 100644
--- a/tools/virsh.pod
+++ b/tools/virsh.pod
@@ -1124,10 +1124,10 @@ I<--config> or I<--current> can be specified. If no flag is specified, behavior
is different depending on hypervisor.
=item B<blockjob> I<domain> I<path> { [I<--abort>] [I<--async>] [I<--pivot>] |
-[I<--info>] [I<--raw>] [I<--bytes>] | [I<bandwidth>] }
+[I<--info>] [I<--raw>] [I<--bytes>] | [I<--bandwidth>] }
Manage active block operations. There are three mutually-exclusive modes:
-I<--info>, I<bandwidth>, and I<--abort>. I<--async> and I<--pivot> imply
+I<--info>, I<--bandwidth>, and I<--abort>. I<--async> and I<--pivot> imply
abort mode; I<--raw> implies info mode; and if no mode was given, I<--info>
mode is assumed.
@@ -1151,7 +1151,7 @@ not supply bytes/s resolution; when omitting the flag, raw output is
listed in MiB/s and human-readable output automatically selects the
best resolution supported by the server.
-I<bandwidth> can be used to set bandwidth limit for the active job.
+I<--bandwidth> can be used to set bandwidth limit for the active job.
Specifying a negative value is interpreted as an unsigned long long
value or essentially unlimited. The hypervisor can choose whether to
reject the value or convert it to the maximum value allowed.
--
2.3.5
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list