From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42779) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b7lP2-0001o2-Kw for qemu-devel@nongnu.org; Tue, 31 May 2016 11:16:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b7lOx-0000OA-TJ for qemu-devel@nongnu.org; Tue, 31 May 2016 11:16:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46907) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b7lOx-0000O5-NM for qemu-devel@nongnu.org; Tue, 31 May 2016 11:16:15 -0400 Date: Tue, 31 May 2016 16:16:11 +0100 From: "Daniel P. Berrange" Message-ID: <20160531151611.GA21628@redhat.com> Reply-To: "Daniel P. Berrange" References: <57470F7C.8020308@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <57470F7C.8020308@redhat.com> Subject: Re: [Qemu-devel] [PULL 10/28] migration: add reporting of errors for outgoing migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Amit Shah , Peter Maydell , Juan Quintela , qemu list , "Dr. David Alan Gilbert" On Thu, May 26, 2016 at 09:00:12AM -0600, Eric Blake wrote: > On 05/26/2016 12:12 AM, Amit Shah wrote: > > From: "Daniel P. Berrange" > > > > 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. Yep, taking care of that now. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|