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"?
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages.
http://libguestfs.org