virsh: man: Document behavior of some blkdeviotune's flags when querying

--live and --config can't be specified together when querying the
configuration, but are valid when setting. The man page was hinting that
they are valid always.
This commit is contained in:
Peter Krempa 2015-01-29 08:33:51 +01:00
parent 20448c2a72
commit 00af238109
1 changed files with 4 additions and 3 deletions

View File

@ -1100,9 +1100,10 @@ cannot be mixed with non-zero values for read or write.
If I<--live> is specified, affect a running guest. If I<--live> is specified, affect a running guest.
If I<--config> is specified, affect the next boot of a persistent guest. If I<--config> is specified, affect the next boot of a persistent guest.
If I<--current> is specified, affect the current guest state. If I<--current> is specified, affect the current guest state.
Both I<--live> and I<--config> flags may be given, but I<--current> is When setting the disk io parameters both I<--live> and I<--config> flags may be
exclusive. If no flag is specified, behavior is different depending given, but I<--current> is exclusive. For querying only one of I<--live>,
on hypervisor. 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>] | =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>] }