Benign error:BF_BFRT FATAL - Unable to find any BfRt Json File

[chrispsommers]

Got an apparently benign error after executing /root/scripts/run_ovs.sh per step 8 on https://github.com/ipdk-io/ipdk/blob/main/build/IPDK_Container/README:

[root@aea8dd7ac07e P4-OVS]# /root/scripts/run_ovs.sh
Killing OVS Processes If Already Running....
Creating /var/run/openvswitch
Starting OvS DB server....
Staring OvS VSWITCHD Process....
2021-11-16T19:38:41Z|00001|vlog|INFO|opened log file /tmp/ovs-vswitchd.log
2021-11-16T19:38:41Z|00002|ovs_numa|INFO|Discovered 12 CPU cores on NUMA node 0
2021-11-16T19:38:41Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 12 CPU cores
WARNING: Logging before InitGoogleLogging() is written to STDERR
I20211116 19:38:41.956179 94197 bf_sde_wrapper.cc:1530] bf_sysfs_fname: /sys/class/bf/bf0/device/dev_add
Install dir: /usr (0x1994410)
bf_switchd: system services initialized
bf_switchd: loading conf_file /usr/share/stratum/target_skip_p4_no_bsp.conf...
bf_switchd: processing device configuration...
Configuration for dev_id 0
  Family        : dpdk
bf_switchd: processing P4 configuration...
P4 profile for dev_id 0
P4 EAL args dummy -n 4 -c 3
num P4 programs 1
  p4_name: dummy
  bfrt_config: 
  port_config: 
  p4_pipeline_name: pipe
    context: 
    config: 
  Pipes in scope [0 1 2 3 ]
  diag: 
  accton diag: 
  non_default_port_ppgs: 0
  SAI default initialize: 1 
Operational mode set to DPDK MODEL
Initialized the device types using PAL handler registration
bf_switchd: drivers initialized
Skipping P4 program load for dev_id 0
EAL: Detected CPU lcores: 12
EAL: Detected NUMA nodes: 1
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 1048576 kB hugepages reported
EAL: VFIO support initialized
TELEMETRY: No legacy callbacks, legacy socket not created
2021-11-16 19:38:42.213563 BF_BFRT FATAL - Unable to find any BfRt Json File
2021-11-16 19:38:42.213715 BF_BFRT ERROR - makeBfRtInfo:383 Failed to create BfRtInfo for dev_id  0

bf_switchd: dev_id 0 initialized

bf_switchd: initialized 1 devices
Skip p4 lib init
Skip mav diag lib init
bf_switchd: spawning cli server thread
bf_switchd: running in background; driver shell is disabled
bf_switchd: server started - listening on port 9999
I20211116 19:38:42.218636 94197 bf_sde_wrapper.cc:1548] switchd started successfully
I20211116 19:38:42.218663 94197 bf_interface.cc:98] Detected is_sw_model: 1
I20211116 19:38:42.218680 94197 bf_interface.cc:99] SDE version: 9.5.0

[stolsma]

Ah, this one I know from Stratum! :laugh:

Stratum/Barefoot daemon code use the given files names as config persistency solution when stratum/Barefoot daemon is rerun, so its more a notification that it didn't find a previous run configuration. In the latest Stratum release this log line definition is moved to informational instead error so probably it will not show here any more too after recompilation in the future...

[asafravid]

@stolsma @mestery seems on my arm64 system this is a FATAL enough error such that it fails the ovs-vswitchd from starting. Hence, Perhaps I should link my fork of https://github.com/asafravid/ovs to this latest stratum change?