Hi. I have very bad issue when booting some servers.
I have infiniband hardware with IPoIB (ip over infiniband).
When sometimes ib network not ready (subnet manager down, link down)
networking service failed to load (systemd-networkd), because it can't
up ib* device. But ovsdb-server can't start
I am using Ubuntu server and the following configuration but sometimes
vmbr0 does not take ip address at all.
so is there any alternative to dhclient?
ovs-vsctl add-br vmbr0
ifconfig vmbr0 up
ovs-vsctl add-bond vmbr0 bond0 enp7s0f0 enp7s0f1 trunks=1529,1530
ovs-vsctl set
On 6/22/2018 9:13 PM, kro...@gmx.com wrote:
Hi all,
I am trying to use OVS (2.5.4) with DPSK on Ubuntu server 16.04.3 (KVM
host) purely for inter-VM communication.
I have been following this guide very closely:
https://help.ubuntu.com/lts/serverguide/DPDK.html
Hi,
Is there a hard
Hello
I looked a bit more into the issue.
This is happenning when OVS receives a CHECKSUM_PARTIAL. For a normal
vm2vm non nsh scenario, OVS provides the same CHECKSUM_PARTIAL to the
receiver which wont then verify the checksum.
But when we are pushing nsh headers, the first receiver may not be
I'm running OVS 2.7.0 on a Linux 3.10.0 kernel. I found a ovs crash.
I doubt it's caused by use-after-free set match->flow = NULL in
minimatch_destroy function with following stack:
(gdb) bt
#0 0x7ff273b71197 in raise () from /usr/lib64/libc.so.6
#1 0x7ff273b72888 in abort () from
