KVM on Fedora 30, Error creating virtual network
-
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.
-
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.
-
I was able to create a virtual network.
-
-
@black3dynamite said in KVM on Fedora 30, Error creating virtual network:
I was able to create a virtual network.
I wonder what is different.
-
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.
-
Can you create it with virsh? Wondering if it's just a virt-manager issue since they are deprecating it.
-
@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.
-
@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?
-
@Doyler3000 Cockpit seems to be the contender to replace virt-manager. Still lacks some functionality but getting better with each update.
-
@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?
-
@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.
-
@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?
-
@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.
-
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!
-
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. -
And in cockpit, clicking on virtual networks causes an "unexpected internal error". So much for that replacing virt-manager.
-
@Doyler3000 said in KVM on Fedora 30, Error creating virtual network:
And in cockpit, clicking on virtual networks causes an "unexpected internal error". So much for that replacing virt-manager.
Are you teaming any network interfaces?
Even with the latest version of cockpit I was still getting the oops response. -
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?
-
@Doyler3000 said in KVM on Fedora 30, Error creating virtual network:
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?
Ooops only appears when I teamed physical interfaces so I think that's cockpit issue.Now I'm not sure about the other error you are getting
