KVM on Fedora 30, Error creating virtual network

Doyler3000

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

JaredBusch

@Doyler3000 said in KVM on Fedora 30, Error creating virtual network:

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

I'm running KVM on Fedora 30 in a few places.

I don't make networks though. I make a team and then use the macvtap, bridged.

Let me try and make one.

JaredBusch

Yup., having a problem. Is this what is happening to you?

Making New:

Results in this error:

Error creating virtual network: The name is not activatable

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/createnet.py", line 811, in _async_net_create
    net.install()
  File "/usr/share/virt-manager/virtinst/network.py", line 244, in install
    net.create()
  File "/usr/lib64/python3.7/site-packages/libvirt.py", line 3007, in create
    if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirt.libvirtError: The name is not activatable

Doyler3000

@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.

Doyler3000

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

Obviously, for a new setup, this could be a huge problem. But for an existing setup, how often are you making new networks?

Making a virtual network should barely happen more often than making a new physical network.

It happens at design time.

Doyler3000

@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.

black3dynamite

I was able to create a virtual network.

black3dynamite

JaredBusch

@black3dynamite said in KVM on Fedora 30, Error creating virtual network:

I was able to create a virtual network.

I wonder what is different.

Doyler3000

@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.

stacksofplates

Can you create it with virsh? Wondering if it's just a virt-manager issue since they are deprecating it.

black3dynamite

@Doyler3000 said in KVM on Fedora 30, Error creating virtual network:

@black3dynamite
And your fedora 30 host was fully up to date?

It was up to date.

Doyler3000

@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?

brandon220

@Doyler3000 Cockpit seems to be the contender to replace virt-manager. Still lacks some functionality but getting better with each update.

FATeknollogee

@stacksofplates said in KVM on Fedora 30, Error creating virtual network:

Wondering if it's just a virt-manager issue since they are deprecating it.

Since when?

stacksofplates

@FATeknollogee said in KVM on Fedora 30, Error creating virtual network:

@stacksofplates said in KVM on Fedora 30, Error creating virtual network:

Wondering if it's just a virt-manager issue since they are deprecating it.

Since when?

The release of RHEL 8. Cockpit is the replacement but it's not at feature parity yet. It feels like what VMware did with the web client and the thick client.

Dashrender

@stacksofplates said in KVM on Fedora 30, Error creating virtual network:

@FATeknollogee said in KVM on Fedora 30, Error creating virtual network:

@stacksofplates said in KVM on Fedora 30, Error creating virtual network:

Wondering if it's just a virt-manager issue since they are deprecating it.

Since when?

The release of RHEL 8. Cockpit is the replacement but it's not at feature parity yet. It feels like what VMware did with the web client and the thick client.

did vmware ever get feature parity?

scottalanmiller

@stacksofplates said in KVM on Fedora 30, Error creating virtual network:

@FATeknollogee said in KVM on Fedora 30, Error creating virtual network:

@stacksofplates said in KVM on Fedora 30, Error creating virtual network:

Wondering if it's just a virt-manager issue since they are deprecating it.

Since when?

The release of RHEL 8. Cockpit is the replacement but it's not at feature parity yet. It feels like what VMware did with the web client and the thick client.

Nice, and... that sucks.

Doyler3000

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!