On 6/27/23 14:02, Barry wrote:
On 27 Jun 2023, at 17:51, Robert McBroom via users
<users@lists.fedoraproject.org> wrote:
Putting
VIRTNETWORKD_ARGS=
in /etc/sysconfig/virtnetworkd
does nothing. Stopping libvirtd allows virt-manager to connect.
Before connection
Does the info here help?
https://discussion.fedoraproject.org/t/libvirtd-stop-responding-after-some-time/84324/3
Seems like a red herring
systemctl stop libvirtd
works a lot simpler and keeps working even with
~]# systemctl status virtnetworkd
○ virtnetworkd.service - Virtualization network daemon
Loaded: loaded (/usr/lib/systemd/system/virtnetworkd.service;
disabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
TriggeredBy: ○ virtnetworkd-ro.socket
○ virtnetworkd-admin.socket
○ virtnetworkd.socket
Docs: man:virtnetworkd(8)
https://libvirt.org
Additional VMs start without problems. so what is the function of
virtnetworkd?
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
