On 7/8/23 17:10, Sam Varshavchik wrote:
ToddAndMargo via users writes:
> Starting libvirtd directly gives:
>
> # /usr/sbin/libvirtd &
> [1] 10957
> /usr/sbin/libvirtd: /lib64/libvirt.so.0: version
> `LIBVIRT_PRIVATE_9.0.0' not found (required by /usr/sbin/libvirtd)
>
>
> And I can not find what provide it:
>
> # dnf whatprovides LIBVIRT_PRIVATE
> Last metadata expiration check: 1:38:19 ago on Sat 08 Jul 2023
> 12:20:14 PM PDT.
> Error: No matches found. If searching for a file, try specifying the
> full path or using a wildcard prefix ("*/") at the beginning.
That's not the right naming convention. The symbol would be
libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit)
[root@monster ~]# dnf whatprovides
'libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit)'
Last metadata expiration check: 2:50:41 ago on Sat 08 Jul 2023 05:18:52
PM EDT.
libvirt-libs-9.0.0-2.fc38.x86_64 : Client side libraries
Repo : fedora
Matched from:
Provide : libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit)
libvirt-libs-9.0.0-3.fc38.x86_64 : Client side libraries
Repo : @System
Matched from:
Provide : libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit)
libvirt-libs-9.0.0-3.fc38.x86_64 : Client side libraries
Repo : updates-released-local
Matched from:
Provide : libvirt.so.0(LIBVIRT_PRIVATE_9.0.0)(64bit)
So, your libvirt-libs package is busted.
# rpm -qa libvirt-libs
libvirt-libs-9.0.0-3.fc38.x86_64
Removing and reinstalling both libvirt-daemon and
libvirt-libs did not change the symptom.
I tried downgrading. That did not help either.