All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1236] [dpdk-23.07]VM crash when start dpdk-l3fwd-power in VM with QEMU-8.0.0
Date: Mon, 22 May 2023 08:15:32 +0000	[thread overview]
Message-ID: <bug-1236-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1236
           Summary: [dpdk-23.07]VM crash when start dpdk-l3fwd-power in VM
                    with QEMU-8.0.0
           Product: DPDK
           Version: 23.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: vhost/virtio
          Assignee: dev@dpdk.org
          Reporter: weix.ling@intel.com
  Target Milestone: ---

[Environment]

DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
23.07.0-rc0
Other software versions: QEMU-8.0.0
OS: Ubuntu 22.04.2 LTS/Linux 5.15.45-051545-generic
Compiler: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
Hardware platform: Purley/IceLake etc.
NIC hardware: Intel(R) Xeon(R) Platinum 8380 CPU @ 2.30GHz
NIC firmware: ice-1.11.14/4.20 0x80017785 1.3346.0

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

1.Bind 1 NIC port to vfio-pci driver:

dpdk-devbind.py --force --bind=vfio-pci 0000:4b:00.0

2.Start dpdk-testpmd as back-end:

x86_64-native-linuxapp-gcc/app/dpdk-testpmd  -l 1-5 -n 8 -a 0000:4b:00.0  \
--vdev net_vhost0,iface=/root/dpdk/vhost-net,queues=4    \
-- -i --nb-cores=4 --rxq=4 --txq=4 --rss-ip
testpmd>start

3.Start VM with QEMU-8.0.0 as front-end:

taskset -c 20,21,22,23,24,25,26,27 /home/QEMU/qemu-8.0.0/bin/qemu-system-x86_64
 -name vm0 -enable-kvm -pidfile /tmp/.vm0.pid \
-daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait -netdev
user,id=nttsip1,hostfwd=tcp:10.239.252.245:6000-:22 -device
e1000,netdev=nttsip1  \
-cpu host -smp 4 -m 8192 -object
memory-backend-file,id=mem,size=8192M,mem-path=/dev/hugepages,share=on -numa
node,memdev=mem -mem-prealloc \
-chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 -device
virtio-serial -device
virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 -vnc :4 \
-drive file=/home/image/ubuntu2004.img -chardev
socket,id=char0,path=/root/dpdk/vhost-net -netdev
type=vhost-user,id=netdev0,chardev=char0,vhostforce,queues=4 \
-device
virtio-net-pci,netdev=netdev0,mac=00:11:22:33:44:55,disable-modern=true,mrg_rxbuf=on,csum=on,mq=on,vectors=10

4.SSH connect VM and build dpdk-l3fwd-power APP, and then start
dpdk-l3fwd-power:

CC=gcc meson -Denable_kmods=True -Dlibdir=lib  --default-library=static
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
meson configure -Dexamples=l3fwd-power x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc

./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power  -c 0xf -n 4
--log-level='user1,7' -- -p 1 -P --config '(0,0,0),(0,1,1),(0,2,2),(0,3,3)'
--no-numa  --parse-ptype --interrupt-only
Show the output from the previous commands.

The VM will crash, when start dpdk-l3fwd-power APP in VM with QEMU-8.0.0, and
it works well when start VM with other QEMU version less than QEMU-8.0.0.

[Expected Result]
Start dpdk-l3fwd-power APP in VM with QEMU-8.0.0 works well, no crash occured.
Regression
Is this issue a regression: (Y/N) N

Maybe this is an Compatibility Issues with QEMU-8.0.0.

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

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

             reply	other threads:[~2023-05-22  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  8:15 bugzilla [this message]
2023-11-06  3:30 ` [Bug 1236] [dpdk-23.07]VM crash when start dpdk-l3fwd-power in VM with QEMU-8.0.0 bugzilla

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-1236-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.