Bug 1880957
Summary: | testpmd crash when restarting it with vhost-user 4 queues + vIOMMU[dpdk] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Pei Zhang <pezhang> |
Component: | dpdk | Assignee: | Maxime Coquelin <maxime.coquelin> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pei Zhang <pezhang> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.3 | CC: | amorenoz, chayang, jinzhao, juzhang, maxime.coquelin, ovs-qe, tredaelli |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-03-21 07:27:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pei Zhang
2020-09-21 09:06:11 UTC
Adrian did the analysis in Bug #1880299. The issue on DPDK side is that the backend assumes there will be no holes in the device's array of virtqueues pointers, but it can happen. Proposed fix is to allocate virtqueues up to requested virtqueue index, so that there are no holes. DPDK series fixing this issue has been posted upstream: http://patches.dpdk.org/user/todo/dpdk/?series=13110 Hello Maxime, With latest rhel8.4 testing, this issue has gone, both dpdk's testpmd and VM keep working well. Could you confirm this fix from code level? Thanks a lot. Versions: dpdk-20.11-1.el8.x86_64 4.18.0-278.rt7.43.el8.dt4.x86_64 qemu-kvm-5.2.0-4.module+el8.4.0+9676+589043b9.x86_64 tuned-2.15.0-1.el8.noarch libvirt-7.0.0-3.module+el8.4.0+9709+a99efd61.x86_64 python3-libvirt-6.10.0-1.module+el8.4.0+8948+a39b3f3a.x86_64 openvswitch2.13-2.13.0-86.el8fdp.x86_64 Best regards, Pei After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |