vnc: add a more descriptive error message
authorAmos Kong <akong@redhat.com>
Sat, 30 Jun 2012 02:02:20 +0000 (10:02 +0800)
committerStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Fri, 13 Jul 2012 09:38:16 +0000 (10:38 +0100)
Currently qemu outputs some low-level error in qemu-sockets.c
when failed to start vnc server.
eg. 'getaddrinfo(127.0.0.1,5902): Name or service not known'

Some libvirt users could not know what's happened with this
unclear error message. This patch added a more descriptive
error message.

Signed-off-by: Amos Kong <akong@redhat.com>
Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
vl.c

diff --git a/vl.c b/vl.c
index 2e140f57c759c31330413704178d4d48a6feaeb3..46248b9c1c77fa2c4e58a4cfa581bf45a6d30f24 100644 (file)
--- a/vl.c
+++ b/vl.c
@@ -3584,8 +3584,11 @@ int main(int argc, char **argv, char **envp)
     /* init remote displays */
     if (vnc_display) {
         vnc_display_init(ds);
-        if (vnc_display_open(ds, vnc_display) < 0)
+        if (vnc_display_open(ds, vnc_display) < 0) {
+            fprintf(stderr, "Failed to start VNC server on `%s'\n",
+                    vnc_display);
             exit(1);
+        }
 
         if (show_vnc_port) {
             printf("VNC server running on `%s'\n", vnc_display_local_addr(ds));