On Thu, Apr 17, 2025 at 06:11:56PM +0100, Daniel P. Berrangé wrote:
> From: Daniel P. Berrangé
>
> When no URI is set we try to guess what daemon to connect to by looking
> for any listening sockets. If there are no listening sockets, however,
> we don't even know what daemon the user expected to
From: Daniel P. Berrangé
Signed-off-by: Daniel P. Berrangé
---
src/remote/remote_sockets.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/src/remote/remote_sockets.c b/src/remote/remote_sockets.c
index 4e6d19098c..b3f6cd6a42 100644
--- a/src/remote/remote_sockets.c
++
For the series:
Reviewed-by: Richard W.M. Jones
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit
From: Daniel P. Berrangé
When no URI is set we try to guess what daemon to connect to by looking
for any listening sockets. If there are no listening sockets, however,
we don't even know what daemon the user expected to connect to. The
error message in this case is not especially clear
This twea
From: Daniel P. Berrangé
The updated doc refers to both the old and new error message, as users
with old deployed versions will still be pointed to the current online
docs URL.
Signed-off-by: Daniel P. Berrangé
---
docs/kbase/failed_connection_after_install.rst | 10 ++
1 file changed,
Daniel P. Berrangé (3):
remote: improve error message when no URI is set
kbase: update docs to account for changed error message
remote: expand some debug messages for socket detection
docs/kbase/failed_connection_after_install.rst | 10 ++
src/remote/remote_sockets.c
We are getting close to 11.3.0 release of libvirt. To aim for the
release on Friday 02 May I suggest entering the freeze on Friday 25
Apr and tagging RC2 on Tuesday 29 Apr.
I hope this works for everyone.
Jirka
Ping. Any opinions / feedback about this?
Thanks,
-Andrea
