aboutsummaryrefslogtreecommitdiff
path: root/cris-dis.c
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2012-10-02 10:02:46 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2012-10-23 13:54:56 +0200
commitf37afb5ab1921f42043b5527a517eef95c36acf8 (patch)
tree19e1c5119272e95f86a51180997532ec37ba3ab8 /cris-dis.c
parente08c95ce8d66276198704f21ed9df6d99b3477e0 (diff)
downloadqemu-f37afb5ab1921f42043b5527a517eef95c36acf8.zip
qemu-f37afb5ab1921f42043b5527a517eef95c36acf8.tar.gz
qemu-f37afb5ab1921f42043b5527a517eef95c36acf8.tar.bz2
migration (outgoing): add error propagation for all protocols
Error propagation is already there for socket backends. Add it to other protocols, simplifying code that tests for errors that will never happen. With all protocols understanding Error, the code can be simplified further by removing the return value. Unfortunately, the quality of error messages varies depending on where the error is detected, because no Error is passed to the NonBlockingConnectHandler. Thus, 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. Before: (qemu) migrate fd:ffff migrate: An undefined error has occurred (qemu) info migrate (qemu) After: (qemu) migrate fd:ffff migrate: File descriptor named 'ffff' has not been found (qemu) info migrate capabilities: xbzrle: off Migration status: failed total time: 0 milliseconds Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'cris-dis.c')
0 files changed, 0 insertions, 0 deletions