On Fri, 2023-08-18 at 18:29 +1000, Ian Laurie wrote:
On 8/18/23 15:38, Ian Laurie wrote:
> 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 forgot to mention.... to even get as far as the reported problem I
also had to do this:
sudo systemctl enable virtqemud
sudo systemctl start virtqemud
I think this needs to be looked into. Before the upgrade stuff was
working fine.
Can you file a bug against libvirt on this, with details of how you
upgraded? Can you also check the DNF logs and see if there's any
relevant-looking output during the upgrade indicating that maybe a
scriptlet went wrong?
I had a quick look at the libvirt spec and it definitely has some stuff
around systemd units on update, but I can't really tell at a quick look
if it's correct/sufficient.
Thanks!
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net