remote: Improve error message when libvirtd isn't running

While this could lead people in the wrong direction, people most commonly
hit this error when libvirtd isn't running, so let's mention a possible
fix.

diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
index 2060cf64111d3d52901085280ae4265e7f7018e6..def4617b5feb39e3f25e7ff0b57243aa8737454c 100644 (file)
--- a/src/remote/remote_driver.c
+++ b/src/remote/remote_driver.c
@@ -724,8 +724,8 @@ doRemoteOpen (virConnectPtr conn,
                 }
             }
             virReportSystemError(errno,
-                                 _("unable to connect to '%s'"),
-                                 sockname);
+              _("unable to connect to '%s', libvirtd may need to be started"),
+              sockname);
             goto failed;
         }