Support and News Forum

Hello community.

I'm trying to run eve-ng 2.0.3-95 (Community. version) in a rack server running Oracle linux 3.10.0-862.11.6 but I'm getting an OVS error when trying to start any node via eve-ng gui. GUI says node started but it stays down and greyed out.
This happens for vIOL, vCSR, vQFX.. so i guess is not node related. i'm running a bit out of ideas as looks to be something to do with openvswitch, maybe? With my shallow knowledge, appears like the ovs cannot find the vunl node when trying to create the bridge.
Doing 'ip link' in the eve-ng (ubuntu) cli, indeed I see plenty of vunl interfaces but all down

Sep 22 19:06:43 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_16
Sep 22 19:06:43 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_32
Sep 22 19:06:43 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_48

This same ova, in my Dell laptop, runs just fine (fedora linux 29)I have tested this with same ova in KVM and VirtualBox hypervisors, same issue.


These are the specs from the host:
Processor Architecture: x86 64-bit
Processors: 2 / 2 (Installed / Maximum)
Processor Summary: Two Intel Xeon Processor Scalable Family
Installed RAM Size: 512 GB


Guest (these are the current settings, but problem is the same with much higher cpu and memory allocated)
# vboxmanage showvminfo "EVE Community VM" | egrep -i "memory|cpu"
Memory size 8192MB
CPU exec cap: 100%
CPUProfile: host
Number of CPUs: 4
CPUID Portability Level: 0
CPUID overrides: None
Configured memory balloon size: 0MB


Thanks a lot in advance for your help!

I guess you missed this part
https://www.eve-ng.net/documentation/in ... equirement

vbox is not supported for sure

Hi Uldis,
Thanks for your reply. I used VBox before (in other hosts) with no issues. Just in case I swicthed to VMWare WS. Imported the vm with plenty of resources (64Gb and 12 cores) and VT-x extensions enabled and working but I get exactly the same problem. This is from the ubuntu (eve-ng) vm logs when trying to boot a single IOL intance:

Sep 23 13:33:39 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_1_16
Sep 23 13:33:39 eve-ng systemd-udevd[7891]: Could not generate persistent MAC address for vunl0_1_16: No such file or directory
Sep 23 13:33:39 eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_1_32
Sep 23 13:33:39 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_1_32
Sep 23 13:33:39 eve-ng systemd-udevd[7851]: Could not generate persistent MAC address for vunl0_1_32: No such file or directory
Sep 23 13:33:39 eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_1_48
Sep 23 13:33:39 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_1_48
Sep 23 13:33:39 eve-ng systemd-udevd[8100]: Could not generate persistent MAC address for vunl0_1_48: No such file or directory

This error might be unrelated but definitely doesn't appear in working eve-ng vms I have in other hosts.


Jaime

As i suspectedd, It looks to be problem with the current eve-ng version. 2.0.3-53 works just fine.
Thanks for the help

eve ng community version is 2.0.3-95 !!!
https://www.eve-ng.net/downloads/eve-ng-2
OVS is removed from eve as unnecessary stuff, same does our bridge network, called as well as vSwitch

I know that:
eve-ng 2.0.3-53 (slighty older version) works OK
eve-ng 2.0.3-95 (current community version) doesn't work for me, showing strange errors about ovs.

Anyway, all works for me now with the older version.