This system cannot be a KVM host : No bridge interfaces like br0 were found

Submitted by yngens on Mon, 05/19/2014 - 21:01

The http://www.webmin.com/cinstall-kvm.html page says:

The install script will replace the systems existing eth0 network interface with a br0 interface with the same address. This is required to create a network bridge that KVM virtual machines can use to talk to the rest of your network. The existing eth0 must have a statically configured IP address for this automatic conversion to work. Once it is done, a reboot is required to activate the new interface.

Unfortunately, it has not as I see the following notices on my Cloudmin UI:

This system cannot be a KVM host : No bridge interfaces like br0 were found

Virtual systems cannot be created or added until this is fixed.

I am going to follow https://www.virtualmin.com/documentation/cloudmin/virtualization/kvm to set it up, but this is to let you know of the issue. Either http://www.webmin.com/cinstall-kvm.html has to be corrected and tell a user has to manually install bridging or the script should be fixed to work with CentOS 6.5.

Status: 
Closed (fixed)

Comments

Submitted by yngens on Wed, 06/04/2014 - 19:41

When I went to Network Configuration pages everything had already been setup correctly. And when I came back to the main page I could see that error notice anymore. Refreshing the window also didn't bring it back. Quite strange. Can't find "Cloudmin Configuration re-check" command like one which is present in Virtualmin UI, is there such a feature?

Submitted by JamieCameron on Mon, 05/19/2014 - 22:23

I had a look, and your system does indeed have a br0 interface.

Where exactly did you see that error message?

Submitted by yngens on Tue, 05/20/2014 - 01:49

Yes, it does. I saw that message just after installing Cloudmin and logging into it. But going to Network settings and coming back made that notice disappear. Strange, but please consider this as closed since the issue is gone. Maybe Cloudmin didn't see the network settings in the very beginning, but then it did later...

Submitted by JamieCameron on Tue, 05/20/2014 - 15:31

Ok, I see the bug that causes that message to temporarily appear - I will fix it in the next Cloudmin release.

Submitted by Issues on Tue, 06/03/2014 - 15:31

Automatically closed -- issue fixed for 2 weeks with no activity.

Submitted by gstlouis on Thu, 01/19/2017 - 14:08

I just setup cloudmin on a new machine and received this error. I didn't know of course this would be resolved if the interface was static when I executed the *.sh file, which it wasn't.

In case this this happens to someone: I setup my interface as static in /etc/sysconfig/network-scripts reboot to make sure aok created a new bridge /etc/sysconfig/network-scripts/ifcfg-br0 ex. DEVICE=br0 TYPE=Bridge ONBOOT=yes BOOTPROTO=static IPADDR=192.168.1.43 NETMASK=255.255.255.0 GATEWAY=192.168.1.1

in the network interface you have to add BRIDGE="br0"

then type: service network restart

cloudmin removed this warning from its dashbaord.

Submitted by JamieCameron on Thu, 01/19/2017 - 18:28

FYI, the next Cloudmin release will automate this process.