On 01/25/2017 10:16 AM, Martin Kletzander wrote:
> For example when both total_bytes_sec and total_bytes_sec_max are set,
> but the former gets cleaned due to new call setting, let's say,
> read_bytes_sec, we end up with this weird message for the command:
> 
>  $ virsh blkdeviotune fedora vda --read-bytes-sec 3000
>  error: Unable to change block I/O throttle
>  error: unsupported configuration: value 'total_bytes_sec_max' cannot be set 
> if 'total_bytes_sec' is not set
> 
> So let's make it more descriptive.  This is how it looks after the change:
> 
>  $ virsh blkdeviotune fedora vda --read-bytes-sec 3000
>  error: Unable to change block I/O throttle
>  error: unsupported configuration: cannot reset 'total_bytes_sec' when 
> 'total_bytes_sec_max' is set
> 
> Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1344897
> 
> Signed-off-by: Martin Kletzander <mklet...@redhat.com>
> ---
>  src/qemu/qemu_driver.c | 46 +++++++++++++++++++++++++++++++---------------
>  1 file changed, 31 insertions(+), 15 deletions(-)

ACK

Michal

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to