[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 10/28] migration: add reporting of errors for out

From: Eric Blake
Subject: Re: [Qemu-devel] [PULL 10/28] migration: add reporting of errors for outgoing migration
Date: Thu, 26 May 2016 09:00:12 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

On 05/26/2016 12:12 AM, Amit Shah wrote:
> From: "Daniel P. Berrange" <address@hidden>
> Currently if an application initiates an outgoing migration,
> it may or may not, get an error reported back on failure. If
> the error occurs synchronously to the 'migrate' command
> execution, the client app will see the error message. This
> is the case for DNS lookup failures. If the error occurs
> asynchronously to the monitor command though, the error
> will be thrown away and the client left guessing about
> what went wrong. This is the case for failure to connect
> to the TCP server (eg due to wrong port, or firewall
> rules, or other similar errors).

> +++ b/qapi-schema.json
> @@ -484,6 +484,10 @@
>  #        throttled during auto-converge. This is only present when 
> auto-converge
>  #        has started throttling guest cpus. (Since 2.7)
>  #
> +# @error-desc: #optional the human readable error description string, when
> +#              @status is 'failed'. Clients should not attempt to parse the
> +#              error strings. (Since 2.6)

Since this is already in a pull request, we may need a followup patch to
fix that to be 2.7.

Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]