On 8/19/23 00:49, Adam Williamson wrote:
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?
OK done:
https://bugzilla.redha
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 d
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 starti
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 t
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
