Hello,
Host 2 is configured with options:remote_ip=192.168.56.142 (host 1 IP).
But I don't think that host 2 is the problem since on host 1 I can see
the arp reply packets coming in on br-eth0 and on eth0. I do not see the
reply packet being forwarded to the vm's port (vnet0).
I'm attaching
Hi,
One of our xenserver 6.1 running
ovs-vsctl (Open vSwitch) 1.4.2
Compiled Nov 23 2012 12:41:37
was showing NFS related error as it was not able to communicate with NFS.
in kernel.log it was showing stack trace with ovs pid in stack.
Can some one tell me does this stack trace show any i
On Sat, Sep 7, 2013 at 4:44 PM, Philippe Gautier
wrote:
> Hello
>
> I am tring to run the following configuration:
>
> kvm client --- net1 interface -- ovs switch -- net2
> interface -- kvm routeur
> eth0 192.168.6.1 tag = 10 br-machines trunks=10,20
> e
same result. segfault on 1.9.3.
[image: Gridcentric Logo]
*Scalable, Efficient, Instant-On Virtualization*
--
Jing Su
Phone: +1-888-365-GRID (x710)
Email: jin...@gridcentric.com
On Sun, Sep 8, 2013 at 1:55 PM, Ben Pfaff wrote:
> On Sat, Sep 07, 2013 at 10:13:57P
On Mon, Sep 9, 2013 at 5:14 AM, Andrei Andone
wrote:
> Hello Jesse,
>
> I tried what you said and to only deal with the br-vnet bridge. I also
> switched to GRE tunnels for ease of viewing packets. Here's how it went:
>
> First config (host h1):
>
>
> [root@localhost ~]# ovs-vsctl show
> 0383aec
On 09/06/2013 07:34 PM, Ben Pfaff wrote:
You can read the section titled "In-Band Control" in the file DESIGN at
the top of the source tree for information about in-band control.
Thanks for the pointer.
If you don't need to use in-band control for IPv6, you can just let
these functions return
Hello Fuhui,
As far as I've read in the virsh man page, `virsh net-define` and `virsh
net-create` have similar functionality.
After you use the `virsh net-define ovs_nat.xml` the ovs_nat network is
created and connected to ovsbr0. Then when you use the `virsh net-create
ovs_nat.xml` you basica
Hello Jesse,
I tried what you said and to only deal with the br-vnet bridge. I also
switched to GRE tunnels for ease of viewing packets. Here's how it went:
First config (host h1):
[root@localhost ~]# ovs-vsctl show
0383aece-fb49-47ab-b9d2-c1ee13c16a89
Bridge br-vnet
Port "vnet0"
