summaryrefslogtreecommitdiffstats
path: root/scripts/vmstate-static-checker.py
diff options
context:
space:
mode:
authorDaniel Henrique Barboza2017-02-22 16:17:29 +0100
committerDr. David Alan Gilbert2017-02-28 12:29:00 +0100
commit87c9cc1c30d2981e9686aaf245b3e2420062f7d4 (patch)
tree3ea0e7152c53cef4a3ee7dbcc48ca78698da1b4a /scripts/vmstate-static-checker.py
parentMerge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into ... (diff)
downloadqemu-87c9cc1c30d2981e9686aaf245b3e2420062f7d4.tar.gz
qemu-87c9cc1c30d2981e9686aaf245b3e2420062f7d4.tar.xz
qemu-87c9cc1c30d2981e9686aaf245b3e2420062f7d4.zip
Changing error message of QMP 'migrate_set_downtime' to seconds
Using QMP, the error message of 'migrate_set_downtime' was displaying the values in milliseconds, being misleading with the command that accepts the value in seconds: { "execute": "migrate_set_downtime", "arguments": {"value": 3000}} {"error": {"class": "GenericError", "desc": "Parameter 'downtime_limit' expects an integer in the range of 0 to 2000000 milliseconds"}} This message is also seen in HMP when trying to set the same parameter: (qemu) migrate_set_parameter downtime-limit 3000000 Parameter 'downtime_limit' expects an integer in the range of 0 to 2000000 milliseconds To allow for a proper error message when using QMP, a validation of the user input was added in 'qmp_migrate_set_downtime'. Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com> Message-Id: <20170222151729.5812-1-danielhb@linux.vnet.ibm.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'scripts/vmstate-static-checker.py')
0 files changed, 0 insertions, 0 deletions