search for: 4e7f20684373

...virt/virtqemud-sock-ro': Connection refused > > (Note: already two socket pathnames and two possible errno values -- 4 > variations.) I think it just needs to give an example or two of the error. People will be able to work out the general pattern. > (2) If the logic from commit 4e7f20684373 fails to make a read-only > connection to libvirtd, we suppress that exception (only log it to the > verbose log), and the user only sees the consequent failure Looking at 4e7f20684373, I think the suppression of the error from the read-only connection was basically a coincidence. We want t...

Fix a small comment typo from commit 4e7f20684373 ("lib: Improve security of in/out sockets when running virt-v2v as root", 2022-03-23). Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2182024 Signed-off-by: Laszlo Ersek <lersek at redhat.com> --- Notes: v2: - new patch lib/utils.mli | 2 +- 1 file changed, 1...

...to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': Connection refused (Note: already two socket pathnames and two possible errno values -- 4 variations.) (2) If the logic from commit 4e7f20684373 fails to make a read-only connection to libvirtd, we suppress that exception (only log it to the verbose log), and the user only sees the consequent failure Failed to connect to '/tmp/v2v.sKlulY/in0': Permission denied There could be further failure modes. If we want to make this consi...

On Tue, Jun 27, 2023 at 07:14:36PM +0200, Laszlo Ersek wrote: > It has frequently tripped us up that on RHEL / Fedora, installing the > right set of libvirt RPMs (such as the one pulled in by > "libvirt-daemon-kvm") does not result in an immediately running libvirt > system instance. Document the need, and the simplest method, for starting > libvirt up manually. >

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2182024 v1 was here: <https://listman.redhat.com/archives/libguestfs/2023-June/031910.html>. Make any "chown_for_libvirt_rhbz_1045069" failure a hard one; that way the user gets to see more direct and more uniform error messages (namely that we couldn't connect to libvirt). Document those connection problems, and a simple