On 04/27/2016 04:05 AM, Daniel P. Berrange wrote: > 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.5) > # > +# @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) 2.7, now -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
