|
From: | Paolo Bonzini |
Subject: | Re: [Qemu-devel] [PATCH 08/25] migration (outgoing): add error propagation for all protocols |
Date: | Wed, 17 Oct 2012 16:50:58 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121009 Thunderbird/16.0 |
Il 17/10/2012 16:43, Markus Armbruster ha scritto: >> > Error propagation is already there for socket backends, even though >> > it is (and remains) incomplete because no Error is passed to the >> > NonBlockingConnectHandler. > Why is that a problem? It means that the exact error message still cannot be sent to the user if the OS reports it asynchronously via SO_ERROR. If NonBlockingConnectHandler received an Error**, we could for example report the error class and/or message via a new field of the query-migration command even if it is reported asynchronously. Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |