Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-1436

[Investigation spike] amd system: ovs process with enable dpdk start failed with dpdk-socket-mem set two socket

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • openvswitch3.5
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • rhel-9
    • None
    • rhel-net-ovs-dpdk
    • ssg_networking

       Problem Description: Clearly explain the issue.

       

       Impact Assessment: Describe the severity and impact (e.g., network down,availability of a workaround, etc.).

      amd system: ovs process with enable dpdk start failed with dpdk-socket-mem set two socket
       

       Software Versions: Specify the exact versions in use (e.g.,openvswitch3.1-3.1.0-147.el8fdp).

      openvswitch3.5-3.5.0-0.19.el9fdp
       

        Issue Type: Indicate whether this is a new issue or a regression (if a regression, state the last known working version).

       

       Reproducibility: Confirm if the issue can be reproduced consistently. If not, describe how often it occurs.

       

       Reproduction Steps: Provide detailed steps or scripts to replicate the issue.

      ovs-vsctl set Open_vSwitch . 'other_config={}'
      ovs-vsctl set Open_vSwitch . other_config:dpdk-socket-mem=1024,1024
      ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=c0000000000000000000000000000000
      ovs-vsctl set Open_vSwitch . other_config:dpdk-lcore-mask=0x1
      ovs-vsctl set Open_vSwitch . other_config:dpdk-init=true
       

       Expected Behavior: Describe what should happen under normal circumstances.

      ovs process with enable dpdk start successfully.
       

       Observed Behavior: Explain what actually happens.

      ovs process with enable dpdk start failed.
       If ovs-vsctl set Open_vSwitch . other_config:dpdk-socket-mem=1024, it has no this issue. It has no this issue when ovs-vsctl set Open_vSwitch . other_config:dpdk-socket-mem=1024,1024 in other intel system.

       Troubleshooting Actions: Outline the steps taken to diagnose or resolve the issue so far.

       

       Logs: If you collected logs please provide them (e.g. sos report, /var/log/openvswitch/* , testpmd console)

      2025-05-29T05:08:04.851Z|00007|dpdk|INFO|Using DPDK 24.11.1
      2025-05-29T05:08:04.851Z|00008|dpdk|INFO|DPDK Enabled - initializing...
      2025-05-29T05:08:04.851Z|00009|dpdk|INFO|EAL ARGS: ovs-vswitchd -c 0x1 --socket-mem 1024,1024 --in-memory.
      2025-05-29T05:08:04.865Z|00010|dpdk|INFO|EAL: Detected CPU lcores: 128
      2025-05-29T05:08:04.865Z|00011|dpdk|INFO|EAL: Detected NUMA nodes: 1
      2025-05-29T05:08:04.865Z|00012|dpdk|INFO|EAL: Detected static linkage of DPDK
      2025-05-29T05:08:04.889Z|00013|dpdk|INFO|EAL: rte_mem_virt2phy(): cannot open /proc/self/pagemap: Permission denied
      2025-05-29T05:08:04.889Z|00014|dpdk|INFO|EAL: Selected IOVA mode 'VA'
      2025-05-29T05:08:04.889Z|00015|dpdk|WARN|EAL: No free 2048 kB hugepages reported on node 0
      2025-05-29T05:08:04.890Z|00016|dpdk|INFO|EAL: VFIO support initialized
      2025-05-29T05:08:04.891Z|00017|dpdk|ERR|EAL: Not enough memory available on socket 1! Requested: 1024MB, available: 0MB
      2025-05-29T05:08:04.891Z|00018|dpdk|EMER|EAL: Cannot init memory
      2025-05-29T05:08:04.891Z|00019|dpdk|EMER|Unable to initialize DPDK: Cannot allocate memory
      2025-05-29T05:08:05.285Z|00002|daemon_unix|ERR|fork child died before signaling startup (killed (Aborted), core dumped)
      2025-05-29T05:08:05.285Z|00003|daemon_unix|EMER|could not detach from foreground session
      

      job: https://beaker.engineering.redhat.com/jobs/11142281

              ovsdpdk-triage ovsdpdk triage
              tli@redhat.com Ting Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: