Hi Ian,
Thanks a ton for looking into this.
Yes we still have the issue.
Attached the ovs log,
The QEMU version is
qemu-system-x86_64 --version
QEMU emulator version 2.10.1(Debian 1:2.10+dfsg-0ubuntu3.5)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
Also we have put in
Hello Ben,
The object maps the name of the table to be monitored
to an array of objects. Each is an
object with the following members:
"columns": [*]optional
"select": optional
As the maps the table name to be monitored to an array
of , my interpretatio
On Mon, Mar 05, 2018 at 10:03:13PM -0800, Anil Jangam wrote:
> Hi,
>
> The RFC7047 states below about the Monitor request.
>
> The request object has the
>
>following members:
>
>o "method": "monitor"
>
>o "params": [, , ]
>
>o "id":
>
>
> The parameter is used to match
On Tue, Mar 06, 2018 at 06:54:30AM +, Josh Bailey via discuss wrote:
> Hoping I'm missing something obvious!
>
> I have a flow like this:
>
> $ grep CONTROLLER sab-dump-flows.log
> cookie=0x5adc15c0, duration=63.446s, table=3, n_packets=60, n_bytes=3436,
> priority=0 actions=CONTROLLER:96
>
Hello all,
I am writing to ask your help about InBand controller
The work in
https://techandtrains.com/2014/04/03/running-open-vswitch-in-network-namespace-inband-controller/
builds the next topology and starts up the controller in h1 ( I did everything
in the website and the topology works well
Hi Anirudh,
Is this still an issue for you?
I tried recreating the issue on my own system following your setup steps but I
did not encounter any issue, I was able to ping both the OVS bridge and
external VMs using vhostuser.
If this is still an issue could your provide the OVS logs for you sy