Eric Blake writes:
> On 02/17/2017 01:01 PM, Daniel Henrique Barboza wrote:
>
200)) {
+(params->downtime_limit < 0 ||
+ params->downtime_limit > MAX_MIGRATE_SET_DOWNTIME)) {
error_setg(errp, QERR_INVALID_PARAMETER_VALUE,
On 02/17/2017 01:01 PM, Daniel Henrique Barboza wrote:
>>> 200)) {
>>> +(params->downtime_limit < 0 ||
>>> + params->downtime_limit > MAX_MIGRATE_SET_DOWNTIME)) {
>>> error_setg(errp, QERR_INVALID_PARAMETER_VALUE,
>>> "downtime_limit",
>>> -
On 02/17/2017 03:37 PM, Paolo Bonzini wrote:
On 17/02/2017 18:26, Daniel Henrique Barboza wrote:
The previous error message was displaying the values in miliseconds,
being misleading with the command that accepts the value in seconds:
{ "execute": "migrate_set_downtime", "arguments": {"value
On 17/02/2017 18:26, Daniel Henrique Barboza wrote:
> The previous error message was displaying the values in miliseconds,
> being misleading with the command that accepts the value in seconds:
>
> { "execute": "migrate_set_downtime", "arguments": {"value": 3000}}
> {"error": {"class": "GenericE
The previous error message was displaying the values in miliseconds,
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
