On 8/18/23 11:40, Ian Laurie wrote:
I upgraded a 38 workstation/server from 38 to 39. The only casualty so far seems to be that virt-manager can no longer launch VMs. Trying to do so results in this: ============================================ Error starting domain: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
OK I've found a way to resolve this as follows: sudo systemctl enable virtnetworkd.socket sudo systemctl restart virtnetworkd.socket I think this will cause some problems for people upgrading. -- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
