Thanks Jesse. I tried the same. Firstly I disconnected interfaces vif4.0, vif5.0, and peth0 from the Bridge eth0 (that Xen created).
Then I created a bridge named br0, and connected peth0, vif4.0, vif5.0 to br0 using ovs-vsctl commands. IP Addresses assigned to peth0 are 10.112.10.50, and to vif4.0 & 5.0 are .53, .52 respectively. I am able to ping from VM1 to VM2 (that is from .53 to .52, even from other hosts in LAN) , but I am not able to ping to the Dom0 (that is .50, either from VMs or from any host in LAN). Is there something I am missing out.? The question that I was asking regarding monitoring of incoming traffic into VMs is, we have one ingress_policing_rate in ovs_vsctl for an interface, but there is no egress/outgress policing rate.. Does that mean that it doesn't have control over incoming traffic onto VMs? * ---------------------------- Thanks & Regards Mohit Dhingra +919611190435* On 8 February 2012 23:03, Jesse Gross <je...@nicira.com> wrote: > On Wed, Feb 8, 2012 at 6:47 AM, Mohit Dhingra <mohitdhing...@gmail.com> > wrote: > > I think, Xen renames eth0 to peth0, and creates a bridge called eth0. > > > > Now, if I create one more bridge br0, using ovs-sctl, does it make sense? > > Should I change the Xen configuration such that Xen doesn't create a > bridge, > > rather it should be created by ovs? Please suggest. > > The physical interface and the VM's interface need to be in the same > bridge. If you are trying to interoperate with existing scripts it > may make sense to use the same name, otherwise it doesn't matter to > OVS. > > > One more question..Does OVS also monitors incoming traffic onto the VMs? > > What do you mean by that? >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
