Peter Krempa
39218865f4
virsh: Require option flags for 'blkdeviotune' arguments
...
Make all of the tunable parameter flags require the option name (don't
parse them positionally).
While techically this would be a breaking change if anyone were to
specify the tunable values positionally this is not the case as the
first two tunables are not compatible with each other:
$ virsh blkdeviotune cd vda 4 5
error: Unable to change block I/O throttle
error: invalid argument: total and read/write of bytes_sec cannot be set at the same time
The above is produced by all implementations of the API (qemu and test
drivers). It is true that the first tunable can be specified
positionally (--total-bytes-sec) but it is misleading and shoud not be
allowed either.
Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
2024-04-02 14:24:29 +02:00
..
2022-04-01 15:33:19 +02:00
2023-11-24 09:53:14 +01:00
2022-10-10 15:06:09 +02:00
2021-11-30 10:45:35 +00:00
2023-11-06 23:45:04 +01:00
2023-08-01 10:46:11 -06:00
2023-11-03 15:56:37 -04:00
2024-03-13 15:02:52 +01:00
2019-12-10 12:41:56 +01:00
2024-04-02 14:24:29 +02:00
2019-07-26 16:48:58 -05:00
2022-06-16 06:43:58 +02:00
2021-09-17 09:40:46 +02:00
2024-01-11 13:15:08 +01:00
2022-03-03 11:06:56 +01:00
2022-10-10 14:31:43 +02:00
2022-10-10 14:31:43 +02:00
2022-06-16 06:43:58 +02:00
2021-09-17 09:40:46 +02:00
2022-06-16 06:43:58 +02:00
2022-01-19 16:48:33 +01:00
2024-01-07 23:57:09 -05:00
2022-04-04 16:30:48 +02:00
2022-06-16 06:43:58 +02:00
2021-09-17 09:40:46 +02:00
2024-02-20 12:08:22 +01:00
2024-02-20 12:08:22 +01:00
2022-06-16 06:43:58 +02:00
2021-09-17 09:40:46 +02:00
2022-06-16 06:43:58 +02:00
2021-09-17 09:40:46 +02:00
2022-06-16 06:43:58 +02:00
2022-03-11 09:10:24 +01:00
2022-06-16 06:43:58 +02:00
2022-03-15 13:36:56 +01:00
2023-10-24 13:51:32 +02:00
2023-10-24 13:51:32 +02:00
2024-04-02 14:24:29 +02:00
2022-03-03 11:06:56 +01:00
2024-03-13 15:02:52 +01:00
2020-01-07 16:12:55 +01:00
2024-04-02 14:24:29 +02:00
2022-02-21 13:34:16 +01:00
2023-04-01 11:40:35 +02:00
2024-04-02 14:24:29 +02:00
2021-07-23 09:59:12 +02:00
2024-03-13 15:02:52 +01:00
2019-06-19 17:12:34 +02:00
2024-04-02 14:24:29 +02:00
2022-01-19 16:48:33 +01:00
2024-03-13 15:02:52 +01:00
2019-08-09 09:03:53 +02:00
2024-03-13 15:02:52 +01:00
2019-06-19 17:12:34 +02:00
2024-03-13 15:02:52 +01:00
2021-06-16 10:32:33 +02:00
2024-03-13 15:02:52 +01:00
2020-08-03 15:30:40 +02:00
2024-04-02 14:24:29 +02:00
2020-08-03 15:30:40 +02:00
2023-11-21 14:43:39 +01:00
2023-08-25 12:36:37 +02:00
2024-03-13 15:02:52 +01:00
2022-03-11 09:10:24 +01:00
2024-03-13 15:02:52 +01:00
2024-04-02 14:24:29 +02:00
2021-04-13 17:00:38 +02:00
2019-06-19 17:12:34 +02:00
2024-03-19 16:34:04 +01:00
2021-04-13 17:00:38 +02:00
2023-09-04 10:31:53 +02:00
2019-06-19 17:12:34 +02:00
2023-09-04 09:35:36 +02:00
2021-10-12 17:28:35 +02:00
2023-04-06 12:48:22 +02:00
2021-06-08 08:52:07 +02:00
2018-10-05 15:53:29 +02:00
2019-06-19 17:12:34 +02:00
2023-09-04 09:35:36 +02:00
2019-06-19 17:12:34 +02:00
2023-04-01 11:40:36 +02:00
2023-04-01 11:40:36 +02:00
2023-03-13 13:29:07 +01:00
2023-04-01 11:40:36 +02:00
2023-05-05 15:08:25 +02:00
2023-06-29 11:51:27 +02:00
2023-12-05 12:21:38 +01:00
2022-07-07 12:21:16 +02:00
2023-08-03 16:41:19 +02:00
2021-12-17 15:05:58 +01:00
2024-04-02 14:24:29 +02:00
2024-04-02 14:24:29 +02:00