Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1221652[details]
log file for ovs-vswitchd
Description of problem:
When starting testpmd in a VM, one of the threads from ovs-vswitchd segfaults with:
[ 4535.253497] vhost_thread2[4613]: segfault at 18 ip 00007fe9e07a9af0 sp 00007fe9d1ee0638 error 4 in ovs-vswitchd[7fe9e06c9000+319000]
Version-Release number of selected component (if applicable):
RHEL7.3
openvswitch-2.5.0-14.git20160727.el7fdp
How reproducible:
Steps to Reproduce:
Configure ovs with the following:
ovsbr0:
dpdk0
vhost-user-1
ovsbr1:
dpdk1
vhostuser-2
vhostuser-3
Create 5 PMD threads, 1 for each port.
create vm1 with 2 vhostuser ports, vhost-user1 and vhost-user-2
create vm2 with 1 vhostuser ports, vhost-user-3
start both VMs
on vm2, bring up the interface with kernel driver (virtio)
on vm1, run testpmd on the two vhostuser interfaces
Actual results:
Once vm1 starts testpmd, the segfault will happen in the host. If vm2 is not started, the segfault will not happen.
Expected results:
There should be no segfault
Additional info:
Created attachment 1221652 [details] log file for ovs-vswitchd Description of problem: When starting testpmd in a VM, one of the threads from ovs-vswitchd segfaults with: [ 4535.253497] vhost_thread2[4613]: segfault at 18 ip 00007fe9e07a9af0 sp 00007fe9d1ee0638 error 4 in ovs-vswitchd[7fe9e06c9000+319000] Version-Release number of selected component (if applicable): RHEL7.3 openvswitch-2.5.0-14.git20160727.el7fdp How reproducible: Steps to Reproduce: Configure ovs with the following: ovsbr0: dpdk0 vhost-user-1 ovsbr1: dpdk1 vhostuser-2 vhostuser-3 Create 5 PMD threads, 1 for each port. create vm1 with 2 vhostuser ports, vhost-user1 and vhost-user-2 create vm2 with 1 vhostuser ports, vhost-user-3 start both VMs on vm2, bring up the interface with kernel driver (virtio) on vm1, run testpmd on the two vhostuser interfaces Actual results: Once vm1 starts testpmd, the segfault will happen in the host. If vm2 is not started, the segfault will not happen. Expected results: There should be no segfault Additional info: