This turned out to be a problem with DHCP configuration on the guests. This works fine now. Thanks for the reply.
Thanks On Wed, Jun 13, 2012 at 6:15 PM, Jesse Gross <je...@nicira.com> wrote: > On Thu, Jun 14, 2012 at 3:30 AM, Abhishek Chanda > <abhishek.li...@gmail.com> wrote: > > Hi all, > > > > I am trying to setup a VLAN with a number of VMs (hosted on Virtualbox) > on a > > blade server host. Here is what I did: > > 1. Installed the OVS kernel module and setup the server > > 2. Created a bridge and two tap devices on the host > > # ovs-vsctl add-br br0 > > 3. Connected the the tap devices to the bridge with a VLAN tag > > # ovs-vsctl add-port br0 tap0 tag=34 > > # ovs-vsctl add-port br0 tap1 tag=34 > > 4. Configured the VMs in bridged mode to use tap0 and tap1 respectively > > 5. Assigned IP addresses to the VMs > > > > But now when I try to ping one VM from another, it succeeds at first and > > then says "Network is unreachable". Initially, both VMs have a routing > table > > populated but after some time the table becomes empty automatically, > that is > > when ping fails. Has this got something to do with my setup? Do I need to > > load the brcompat module too? > > If something's changing your routing table then that's outside the scope > of OVS. >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
