CentOS automatically created virbr0 and virbr0-nic and killed my cloud services (?)



  • @scottalanmiller

    Guten Morgen guys and gals, been running the CentOS for a good while now and it seemed pretty stable, so I move our production cloud to it.

    This morning the cloud was down, it was coming up with a certificate error. On my vSphere client I could only see the 192.168.122.0 IP address on the VM, the IP for the cloud was not being shown. I was still able to connect to it with webmin, so I checked out the NIC's first. 2 new virtual NICs had been created, virbr0 and virbr0-nic with a subnet of 192.168.122.0. I was unable to deactivate the nic's, so I virsh net-destroy'ed them. Everything is back on track, but I have some questions. Were they the probable cause for no connectivity? What created them? I have not installed any virtual server services. Are the services included in the default CentOS install?



  • You have libvirt installed that's why the virbr0 nics where created and you could delete them with virsh.

    It is not part of the default Centos 7 minimal install.



  • Since you are using vSphere client, you must be using VMware as your hypervisor.

    It is indeed really strange why Kvm virtualization packages would be installed in your vms.



  • @Romo said in CentOS automatically created virbr0 and virbr0-nic and killed my cloud services (?):

    You have libvirt installed that's why the virbr0 nics where created and you could delete them with virsh.

    It is not part of the default Centos 7 minimally install.

    Thanks Romo. It is probably included in the gnome package. I had installed the gnome desktop to get a look at centos. After some further testing I am beginning to think that the problem didn't have anything to do with the vnic's, though.



  • Yes if you installed gnome, it probably installed gnome-boxes which is an application to manage vms so that's why it installed libvirt.

    After some further testing I am beginning to think that the problem didn't have anything to do with the vnic's, though.

    Yeah, probably nothing to do with the outage, hope you find the true problem.


Log in to reply
 

Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.