On Tue, Nov 20, 2012 at 05:44:30PM +0900, Simon Horman wrote:
> I believe I have found a regression that affects the behaviour of the
> datapath. A quick bisection points to the following patch:
>
> acf60855126bcfa79ea22d7846af5f2efe26cd30
> ofproto-dpif: Use a single underlying datapath across multiple bridges.
>
>
> For my test I run Open vSwtich inside a kvm VM. Inside the VM
> there are two ethernet interfaces, eth0 and eth1 although only
> eth1 is used in this test. The interfaces are emulated and
> the other end of eth1 is tap1 in the host.
>
> eth1 has been added to an Open vSwtich bridge in the VM.
> The output of ovs-vsctl show is as follows:
>
> cff268ec-4e3d-41fa-8127-efa2bb851ae7
> Bridge "br0"
> Port "eth1"
> Interface "eth1"
> Port "br0"
> Interface "br0"
> type: internal
> ovs_version: "1.9.90"
>
> When I try to from the host to the VM I obvserve that the VM
> does not respond to ARP requests.
>
> COnversely, when I try to ping from the VM to the host it appears
> that the VM ignores ARP responses.
I think that Justin was debugging some userspace datapath[*] problems
late last week. I remember discussing fixes with him. It looks like he
didn't send out the fix before he left on vacation, which means that
they weren't quite ready yet. I imagine he'll finish it up and send it
up next Monday when he gets back.
[*] This is userspace datapath-specific, right? The only place you
mentioned the userspace datapath was in the Subject.
In the meantime, I apologize for the inconvenience. The "single
datapath" model still needs some fine-tuning, but it's necessary to make
the new tunneling model work properly.
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
