Re: [PATCH 2/2] Report better error message in remoteGetUNIXSocket
On Wed, Nov 29, 2023 at 10:09:36AM +0000, Richard W.M. Jones wrote:
On Wed, Nov 29, 2023 at 09:49:47AM +0000, Richard W.M. Jones wrote:
> I'd like to try writing a wiki page that we can link in this message,
> since I have to explain this problem over and over again to people and
> it'd be good to have one place that explains it.
It's a start:
https://gitlab.com/libvirt/libvirt-wiki/-/merge_requests/6
I realise after writing it that I don't fully understand the problem
myself.
Why is it exactly that the socket doesn't work after installation, but
does work after reboot? On my laptop, the socket unit is set to
"disabled", yet libvirt works fine (since the laptop has been rebooted
since libvirt was installed, I guess). Shouldn't the command be
"systemctl enable virtqemud.socket --now"?
It's a distro policy.
I assume you're running Fedora/RHEL on your laptop, and the policy
there is that services (or sockets) should not be started right after
a package is installed. Debian has the opposite policy.
This is in no way specific to libvirt. For example, [1] describes how
to set up Apache on RHEL, and as you can see manually starting the
service after installation is an explicitly documented step.
Regarding why the socket is disabled, are you sure that you're
looking at the actual status rather than the preset? I've made some
improvement to that area recently[2] so things should be less
confusing going forward.
Additionally, virtqemud.service BindsTo=virtqemud.socket, so even if
the socket is disabled, the service being enabled will be enough to
cause it to be started on boot.
[1]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/...
[2] https://src.fedoraproject.org/rpms/fedora-release/pull-request/281
--
Andrea Bolognani / Red Hat / Virtualization