Yeah, I'm really familiar with the standard linux bridge methods, but not so much on OVS. It seems a bit strange to me that you only have a bridge 'cloudbr' and the traffic labels refer to ports rather than bridges, but what do I know.
There are lots of ways to configure networking. If you want to run all networks off of something trunked from eth0, you might try pointing all traffic labels at your 'cloudbr' and see if cloudstack can create the other bridges. You may have to create the management bridge manually. This is usually set up as the only bridge in single interface setups, and then all traffic labels point to that bridge so cloudstack can bring up trunks and bridges from there. On Wed, May 6, 2015 at 8:32 AM, Aleksandr Ivanov <ad...@rnet.ru> wrote: > I did everything according to manual > > http://cloudstack-installation.readthedocs.org/en/latest/hypervisor/kvm.html > Default service offering is working good ( every vnet is made in bridge > where it should be and etc ) > So should I open a bug ? Because I dont see that something is even trying > to > create OVS tunnels. > > >
