DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/vhost/virtio Bug 1462] [dpdk-24.07] virtio_smoke/test_virtio_loopback: Vhost or Virtio hang
Date: Mon, 17 Jun 2024 02:54:30 +0000	[thread overview]
Message-ID: <bug-1462-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 4900 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1462

            Bug ID: 1462
           Summary: [dpdk-24.07] virtio_smoke/test_virtio_loopback: Vhost
                    or Virtio hang
           Product: DPDK
           Version: 24.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: vhost/virtio
          Assignee: dev@dpdk.org
          Reporter: yux.jiang@intel.com
  Target Milestone: ---

[Environment]

DPDK version: 24.07.0-rc0
OS: Ubuntu 22.04.3 LTS; 5.15.0-82-generic
Compiler: gcc version 11.4.0
Hardware platform: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz

[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.

1.Build dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=True -Dlibdir=lib  --default-library=static
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc

2.Launch vhost as client mode
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-3 -n 4  --file-prefix=vhost
--no-pci --vdev 'eth_vhost0,iface=vhost-net,client=1,queues=8'   -- -i
--nb-cores=2 --rxq=2 --txq=2

3, Launch virtio-user as server mode
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 4-6 -n 4  --file-prefix=virtio1
--no-pci --vdev
'net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-net,server=1,queues=8,mrg_rxbuf=1,in_order=1'
  --single-file-segments -- -i --tx-offloads=0x0 --enable-hw-vlan-strip
--rss-ip --nb-cores=2 --rxq=8 --txq=8

[Actual Result]
Vhost hang's log 
root@dut214:~/dpdk# x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-3 -n 4 
--file-prefix=vhost --no-pci --vdev
'eth_vhost0,iface=vhost-net,client=1,queues=8'   -- -i --nb-cores=2 --rxq=2
--txq=2
EAL: Detected CPU lcores: 112
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/vhost/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=163456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc

Warning! port-topology=paired and odd forward ports number, the last port will
pair with itself.

Configuring Port 0 (socket 0)
VHOST_CONFIG: (vhost-net) vhost-user client: socket created, fd: 33
VHOST_CONFIG: (vhost-net) Setting max queue pairs to 8

Virtio-user hang, vhost's log:
root@dut214:~/dpdk# x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-3 -n 4 
--file-prefix=vhost --no-pci --vdev
'eth_vhost0,iface=vhost-net,client=1,queues=8'   -- -i --nb-cores=2 --rxq=2
--txq=2
EAL: Detected CPU lcores: 112
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/vhost/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=163456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc

Warning! port-topology=paired and odd forward ports number, the last port will
pair with itself.

Configuring Port 0 (socket 0)
VHOST_CONFIG: (vhost-net) vhost-user client: socket created, fd: 33
VHOST_CONFIG: (vhost-net) Setting max queue pairs to 8
VHOST_CONFIG: (vhost-net) failed to connect: No such file or directory
VHOST_CONFIG: (vhost-net) reconnecting...
Port 0: 56:48:4F:53:54:00
Checking link statuses...
Done
testpmd> VHOST_CONFIG: (vhost-net) connected
VHOST_CONFIG: (vhost-net) new device, handle is 0

testpmd>



[Expected Result]
Not hang
root@dut214:~/dpdk# x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-3 -n 4 
--file-prefix=vhost --no-pci --vdev
'eth_vhost0,iface=vhost-net,client=1,queues=8'   -- -i --nb-cores=2 --rxq=2
--txq=2
EAL: Detected CPU lcores: 112
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/vhost/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=163456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc

Warning! port-topology=paired and odd forward ports number, the last port will
pair with itself.

Configuring Port 0 (socket 0)
VHOST_CONFIG: (vhost-net) vhost-user client: socket created, fd: 33
VHOST_CONFIG: (vhost-net) Setting max queue pairs to 8
VHOST_CONFIG: (vhost-net) failed to connect: No such file or directory
VHOST_CONFIG: (vhost-net) reconnecting...
Port 0: 56:48:4F:53:54:00
Checking link statuses...
Done
testpmd> 


[Regression]
Is this issue a regression: (Y)
Bad commit id1: ///////Virtio hang
02a7ca5114 vhost: improve fdset initialization
Bad commit id2: ///////vhost hang
c23f6373c8 vhost: hide synchronization within FD manager

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 6818 bytes --]

                 reply	other threads:[~2024-06-17  2:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1462-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).