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
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup self._backend.create() File "/usr/lib64/python3.12/site-packages/libvirt.py", line 1373, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory ============================================
Can anyone offer some insight before I create a BZ for this? I suspect it is an upgrade issue maybe?
Thanks, Ian
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney