On 6/19/23 14:57, Thomas Cameron wrote:
On 6/19/23 12:33, Jonathan Billings wrote:
On Mon, Jun 19, 2023 at 11:55:26AM -0500, Thomas Cameron wrote:
I have a dedicated Fedora 38 KVM hypervisor that I use for testing,
and I
also use my desktop to run VMs. When I leave the virtualization
manager app
open (typically overnight), it has disconnected from the remote
hypervisor
and from my local hypervisor. When I double click the connection, it
just
hangs. If I restart libvirtd on the hypervisor and on my desktop, it
connects instantly.
Is anyone else seeing this?
I have seen something like this, only connecting to the local service.
I was able to resolve it using the fix in Comment 4 of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2213660#c4
Many thanks, Jonathan. I've implemented that config file, we'll see
how to goes!
Had this problem start sometime last week. Found that stopping libvirtd
would let virt-manager connect. Saw that it has occurred in the past and
setting a variable in /etc/conf.d was suggested. Didn't help.
Trying the /etc/sysconfing/virtnetworkd variable from the bugzilla link.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
