Hi,
Thanks for the help.
Bonding tap or internal devices are not my use case.
I saw the interface status was UP and RUNNING (for both eth0 and eth1) in
my setup and still did not get the enabled state in bond show.
This is the exact issue I am observing.
On Mon, 13 Feb 2017 at 4:45 PM, nic
> -Original Message-
> From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-
> boun...@openvswitch.org] On Behalf Of Devanath S
> Sent: Monday, February 13, 2017 6:30 AM
> To: ovs-discuss@openvswitch.org
> Subject: [ovs-discuss] Fwd: netdev-dpdk: add hotplug support
>
> Hi,
>
>
> On Feb 12, 2017, at 11:26 PM, Ronaldo Resende wrote:
>
> ronaldo@localhost:~$ sudo ovs-vsctl add-bond s1 bond0 s1-eth9 s1-eth10
> ovs-vsctl: cannot create an interface named s1-eth9 because a port named
> s1-eth9 already exists on bridge s1
>
> Any other thoughts?
The s1-eth9 and s1-eth10 h
> On Feb 12, 2017, at 1:05 PM, nickcooper-zhangtonghao
> wrote:
>
> If you use the virtual ethernet driver, you should set the type of net
> device. If not, the “system” will be used.
>
> For example, tap device
>
> ovs-vsctl add-br br0
> ifconfig tap1 up
> ifconfig tap2 up
> ovs-vsctl add-
