One last tiny bug for Fedora fix:
virt-manager timeout on first attempt
https://bugzilla.redhat.com/show_bug.cgi?id=2221811
I just have to remember to start virt-mamager,
kill it, and restart it.
This is probably a timing issue.
___
users mailing list
Samuel Sieb wrote:
> On 2023-07-09 18:01, ToddAndMargo via users wrote:
>> The file should have not been used to create the
>> links. The links should have been created based
>> on the reviion of libvirtd
>
> Why not? That's exactly what ldconfig does. It creates links to the latest
> version o
On 2023-07-09 23:39, ToddAndMargo via users wrote:
On 7/9/23 22:45, Samuel Sieb wrote:
On 2023-07-09 18:01, ToddAndMargo via users wrote:
On 7/9/23 13:03, Samuel Sieb wrote:
On 7/9/23 03:52, ToddAndMargo via users wrote:
9005 came from upstream and Fedora repo not removing
their garbage when
On 7/9/23 22:45, Samuel Sieb wrote:
On 2023-07-09 18:01, ToddAndMargo via users wrote:
On 7/9/23 13:03, Samuel Sieb wrote:
On 7/9/23 03:52, ToddAndMargo via users wrote:
9005 came from upstream and Fedora repo not removing
their garbage when when dnf remove was issued, which
is the second bug.
On 2023-07-09 18:01, ToddAndMargo via users wrote:
On 7/9/23 13:03, Samuel Sieb wrote:
On 7/9/23 03:52, ToddAndMargo via users wrote:
9005 came from upstream and Fedora repo not removing
their garbage when when dnf remove was issued, which
is the second bug.
How is this anything to do with th
On 7/9/23 15:51, Jeffrey Walton wrote:
On Sun, Jul 9, 2023 at 4:03 PM Samuel Sieb wrote:
On 7/9/23 03:52, ToddAndMargo via users wrote:
9005 came from upstream and Fedora repo not removing
their garbage when when dnf remove was issued, which
is the second bug.
How is this anything to do wit
On 7/9/23 13:03, Samuel Sieb wrote:
On 7/9/23 03:52, ToddAndMargo via users wrote:
9005 came from upstream and Fedora repo not removing
their garbage when when dnf remove was issued, which
is the second bug.
How is this anything to do with the Fedora repo when that file came from
a third-part
On 7/9/23 15:18, Sam Varshavchik wrote:
ToddAndMargo via users writes:
On 7/9/23 04:21, Sam Varshavchik wrote:
ToddAndMargo via users writes:
Okay, after erasing all the 9005's, redoing the following
https://www.libvirt.org/daemons.html#switching-to-modular-daemons
and rebooting, all my V
On Sun, Jul 9, 2023 at 4:03 PM Samuel Sieb wrote:
>
> On 7/9/23 03:52, ToddAndMargo via users wrote:
> > 9005 came from upstream and Fedora repo not removing
> > their garbage when when dnf remove was issued, which
> > is the second bug.
>
> How is this anything to do with the Fedora repo when tha
ToddAndMargo via users writes:
On 7/9/23 04:21, Sam Varshavchik wrote:
ToddAndMargo via users writes:
Okay, after erasing all the 9005's, redoing the following
https://www.libvirt.org/daemons.html#switching-to-modular-daemons
and rebooting, all my VM stuff is running perfectly again.
Than
On 7/9/23 03:52, ToddAndMargo via users wrote:
9005 came from upstream and Fedora repo not removing
their garbage when when dnf remove was issued, which
is the second bug.
How is this anything to do with the Fedora repo when that file came from
a third-party something?
___
On Sun, 09 Jul 2023 05:16:14 -0700 ToddAndMargo via users wrote:
> On 7/9/23 04:16, Sam Varshavchik wrote:
>> I don't know what libvirt.so.0.9005.0 is.
> It is upstream's version. Their remove scripts left
> it in place. Fedora's remove script does the
> same thing.
AFAIK there is no remove sc
On 7/9/23 04:16, Sam Varshavchik wrote:
I switched back.
I don't know what libvirt.so.0.9005.0 is.
It is upstream's version. Their remove scripts left
it in place. Fedora's remove script does the
same thing.
When rebooting libvert looks for the latest version
and creates links to them. It
On 7/9/23 04:21, Sam Varshavchik wrote:
ToddAndMargo via users writes:
Okay, after erasing all the 9005's, redoing the following
https://www.libvirt.org/daemons.html#switching-to-modular-daemons
and rebooting, all my VM stuff is running perfectly again.
Thank you all for the help!
Upstrea
On Sun, 9 Jul 2023, Sam Varshavchik wrote:
ToddAndMargo via users writes:
On 7/8/23 18:38, ToddAndMargo via users wrote:
On 7/8/23 17:26, Chris Adams wrote:
Once upon a time, ToddAndMargo said:
# rpm -qa libvirt-libs
libvirt-libs-9.0.0-3.fc38.x86_64
Removing and reinstalling both libvirt-
ToddAndMargo via users writes:
Okay, after erasing all the 9005's, redoing the following
https://www.libvirt.org/daemons.html#switching-to-modular-daemons
and rebooting, all my VM stuff is running perfectly again.
Thank you all for the help!
Upstream documentation, like that, isn't really
ToddAndMargo via users writes:
On 7/8/23 18:38, ToddAndMargo via users wrote:
On 7/8/23 17:26, Chris Adams wrote:
Once upon a time, ToddAndMargo said:
# 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 sy
On 7/9/23 02:49, Jeffrey Walton wrote:
On Sun, Jul 9, 2023 at 12:16 AM ToddAndMargo via users
wrote:
On 7/8/23 20:57, Samuel Sieb wrote:
On 7/8/23 18:45, ToddAndMargo via users wrote:
# libvirtd --daemon
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not
found (required by /l
On Sun, Jul 9, 2023 at 12:16 AM ToddAndMargo via users
wrote:
>
> On 7/8/23 20:57, Samuel Sieb wrote:
> > On 7/8/23 18:45, ToddAndMargo via users wrote:
> >> # libvirtd --daemon
> >> libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not
> >> found (required by /lib64/libvirt-lxc.so.0)
On 7/8/23 21:35, ToddAndMargo via users wrote:
After rebooting, my links were changed back:
libvirt-admin.so.0.9005.0
libvirt-lxc.so.0.9005.0
libvirt-qemu.so.0.9005.0
libvirt.so.0.9005.0
So I erased the links and the 9005 files too.
# systemctl status libvirtd.service
is happy after stopping
On 7/9/23 00:16, ToddAndMargo via users wrote:
On 7/8/23 20:57, Samuel Sieb wrote:
On 7/8/23 18:45, ToddAndMargo via users wrote:
# libvirtd --daemon
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not
found (required by /lib64/libvirt-lxc.so.0)
libvirtd: /lib64/libvirt.so.0: ve
On 7/8/23 21:16, ToddAndMargo via users wrote:
On 7/8/23 20:57, Samuel Sieb wrote:
On 7/8/23 18:45, ToddAndMargo via users wrote:
# libvirtd --daemon
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not
found (required by /lib64/libvirt-lxc.so.0)
libvirtd: /lib64/libvirt.so.0: ve
On 7/8/23 21:16, ToddAndMargo via users wrote:
# systemctl start libvirtd
And status shows good too !!
"virsh-manager" still does ont work. but...
And restarting libvirtd.service and it is back
to complaining again. But I will reboot
and get back
And starting libvirtd the correct way:
#
On 7/8/23 20:57, Samuel Sieb wrote:
On 7/8/23 18:45, ToddAndMargo via users wrote:
# libvirtd --daemon
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not
found (required by /lib64/libvirt-lxc.so.0)
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not
found (requir
On 7/8/23 18:45, ToddAndMargo via users wrote:
# libvirtd --daemon
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not found
(required by /lib64/libvirt-lxc.so.0)
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not found
(required by /lib64/libvirt-qemu.so.0)
Act
On 7/8/23 18:45, ToddAndMargo via users wrote:
On 7/8/23 18:38, ToddAndMargo via users wrote:
On 7/8/23 17:26, Chris Adams wrote:
Once upon a time, ToddAndMargo said:
# rpm -qa libvirt-libs
libvirt-libs-9.0.0-3.fc38.x86_64
Removing and reinstalling both libvirt-daemon and
libvirt-libs did no
On 7/8/23 18:38, ToddAndMargo via users wrote:
On 7/8/23 17:26, Chris Adams wrote:
Once upon a time, ToddAndMargo said:
# 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. Tha
On 7/8/23 17:26, Chris Adams wrote:
Once upon a time, ToddAndMargo said:
# 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.
If I had to guess, I'd
Once upon a time, ToddAndMargo said:
> # 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.
If I had to guess, I'd say you have some other li
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:
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
On 7/8/23 13:56, ToddAndMargo via users wrote:
On 7/8/23 04:33, Peter Boy wrote:
Am 08.07.2023 um 09:13 schrieb ToddAndMargo via users
:
no symptom change after a reboot either.
I do not think there were to many tries.
Or five attempts failed right in a row
when I issued start
You shou
On 7/8/23 04:33, Peter Boy wrote:
Am 08.07.2023 um 09:13 schrieb ToddAndMargo via users
:
no symptom change after a reboot either.
I do not think there were to many tries.
Or five attempts failed right in a row
when I issued start
You should use journalctl to check the log entries in de
> Am 08.07.2023 um 09:13 schrieb ToddAndMargo via users
> :
>
> no symptom change after a reboot either.
>
> I do not think there were to many tries.
>
> Or five attempts failed right in a row
> when I issued start
>
You should use journalctl to check the log entries in detail. This kind of
no symptom change after a reboot either.
I do not think there were to many tries.
Or five attempts failed right in a row
when I issued start
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedo
Fedora 38
# systemctl is-active virtqemud.socket
failed
# systemctl is-active virtqemud.service
failed
# systemctl start libvirtd
Job for libvirtd.service failed because the control process exited with
error code.
See "systemctl status libvirtd.service" and "journalctl -xeu
libvirtd.service
36 matches
Mail list logo
