@black3dynamite

I've got two physical interfaces in a team, on the bridge that the production VMs are on.

You think this relates to the "Ooops" ? or the "name not activatable" error?

And in cockpit, clicking on virtual networks causes an "unexpected internal error". So much for that replacing virt-manager.

In the interests of reopening the previous closure, virtual networks are broken again. I can't create or start virtual networks. Same 'name is not activatable ' rubbish
Annoying.

In the interests of "closure", the plethora of libvirt updates which came down the line yesterday from fedora seem to have fixed the problem. I can now create virtual networks again. Yay!

@stacksofplates
Yes I just tried creating it with virsh and it was created without a problem.
However starting it leads to the same error: The name is not activatable.

I didn't realise virt-manager was being deprecated. Is there a replacement planned?

@black3dynamite

And your fedora 30 host was fully up to date?

I've finally found someone referencing the same error message: https://forums.whonix.org/t/installing-kvm-conflicting-directions/7582

It was 4 days ago so agrees with the theory that the error is caused by a very recent change in the packages.

@JaredBusch

Sure - but the reason I noticed this is because the test-network (which I setup when I setup the host) stopped working so the test machines connected to it lost their network. I couldn't reactivate this. The error message was the same as when trying to create a new virtual network.

Fortunately these are test machines so I can live without it for the moment.

A second test-network I'd set up on the same host is still working, which is strange.

Thanks for testing - glad it's not just me! I haven't been able to find anything relating to the error on google. Maybe I just need to wait a few days to see if a fix comes along.

@JaredBusch
I use a bridge onto the LAN for the production stuff. I've also got a test network that I created through virt-manager using most of the defaults that's just available internally to the host.

Edit: just seen your reply. Yes that's exactly what's happening for me.

Hi all,

Is anyone running KVM on Fedora 30?
I think as a result of some recent OS updates, sometime between last Wednesday and today, I've lost the ability to create virtual networks (at least through virt-manager).

Error message is: Error creating virtual network: The name is not activatable

Anyone else seeing similar?

Thanks