DPDK usage discussions
 help / color / mirror / Atom feed
From: cuyu tang <me@expoli.tech>
To: users@dpdk.org
Subject: Pktgen failing in a virtualbox virtual machine
Date: Thu, 31 Oct 2024 17:57:04 +0800	[thread overview]
Message-ID: <55BFBAE329D6694E+feadbf99-bbe5-485b-952c-ba22b8815166@expoli.tech> (raw)

I'm having segfault issues when running pktgen in a virtualbox virtual 
machine.

Here's what I run it in and some details about running the commands,

and what I can do to get it to run correctly


pktgen version: git main brunch

# git log
commit cc1d4c606dea3939adf75cc02de0f7cf2b28cf1e (HEAD -> main, tag: 
pktgen-24.07.0, origin/main, origin/HEAD)

dpdk version: dpdk-24.07

[root@localhost dpdk-24.07]# ./usertools/dpdk-devbind.py -s

Network devices using DPDK-compatible driver
============================================
0000:00:09.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio 
unused=e1000,vfio-pci
0000:00:0a.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio 
unused=e1000,vfio-pci

pktgen run command:

gdb --args /root/pktgen-dpdk/usr/local/bin/pktgen -m 1.0

Port DevName          Index NUMA PCI Information   Src MAC           
Promiscuous
Thread 1 "pktgen" received signal SIGSEGV, Segmentation fault.
0x000000000043c38b in dump_device_info () at ../app/pktgen-port-cfg.c:102
102             pkt   = &pinfo->seq_pkt[SINGLE_PKT];

(gdb) bt
#0  0x000000000043c38b in dump_device_info () at 
../app/pktgen-port-cfg.c:102
#1  0x000000000043e3cf in pktgen_config_ports () at 
../app/pktgen-port-cfg.c:325
#2  0x000000000043aa23 in main (argc=1, argv=0x7fffffffe2d8) at 
../app/pktgen-main.c:465

(gdb) n
89                  bus = rte_bus_find_by_device(dev.device);
(gdb)
90              if (bus && !strcmp(rte_bus_name(bus), "pci")) {
(gdb)
94                  vend[0] = device[0] = '\0';
(gdb)
95                  sscanf(rte_dev_bus_info(dev.device), "vendor_id=%4s, 
device_id=%4s", vend, device);
(gdb)
97                  rte_eth_dev_get_name_by_port(i, name);
(gdb)
98                  snprintf(buff, sizeof(buff), "%s:%s/%s", vend, 
device, rte_dev_name(dev.device));
(gdb)
90              if (bus && !strcmp(rte_bus_name(bus), "pci")) {
(gdb)
101             pinfo = l2p_get_port_pinfo(i);
(gdb)
102             pkt   = &pinfo->seq_pkt[SINGLE_PKT];
(gdb)

Thread 1 "pktgen" received signal SIGSEGV, Segmentation fault.
0x000000000043c38b in dump_device_info () at ../app/pktgen-port-cfg.c:102
102             pkt   = &pinfo->seq_pkt[SINGLE_PKT];
(gdb) p pinfo
$3 = (port_info_t *) 0x0
(gdb)




             reply	other threads:[~2024-11-02 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31  9:57 cuyu tang [this message]
2024-11-02 16:03 ` Stephen Hemminger
2024-11-03 15:36   ` Wiles, Keith
2024-11-03 15:53     ` Stephen Hemminger
2024-11-03 16:34       ` Wiles, Keith
2024-11-01  1:18 cuyu tang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55BFBAE329D6694E+feadbf99-bbe5-485b-952c-ba22b8815166@expoli.tech \
    --to=me@expoli.tech \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).