virbr0 is created automatically by libvirt, not OpenNebula. This bridge is not connected to any interface so it won't have external connectivity. In case you want to use virbr make sure it adds an eth interface but from my experience it is more useful to create the interface in the OS configuration and do not use virbr0.
You can disable that bridge with: # virsh net-destroy default # virsh net-autostart default --disable On Wed, Sep 18, 2013 at 2:12 PM, <kenny.ke...@bol.com.br> wrote: > Hello. > > I have some problems with xen 4.2 and opennebula 4.2 networking. > > In the past just with xen without opennebula, I used xenbr0 and it works > ok, but after opennebula, it installs vifbr0 (libvirtd). > > what i need to do to xen works with vifbr0 like it works with xenbr0(bridge) > ? > > I try to work with the two bridges (vifbr0 and xenbr0), but it doesnt work. > > Thanks. > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > -- Join us at OpenNebulaConf2013 in Berlin from the 24th to the 26th of September 2013! Javier Fontán Muiños Developer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org | @OpenNebula | github.com/jfontan _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
