Peter, Could you please attach a core? Thanks, fbl
Hi, Flavio, I am using my current environment with other tests, I am just afraid replacing packages might break something. Sorry for not being able to provide the core now. I was thinking that the backtrace is meaningful enough, so I didn't keep the core. I will keep it next time when I encounter problems. If you would not mind, I would suggest the following options: 1. Do you have any free environment to test? I think using these packages: openvswitch-dpdk-2.4.0-0.10346.git97bab959.1.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7.x86_64 And then start testpmd in the guest should possibly trigger the bug (at least 100% for me before, if nothing important I missed). When the bug triggers, guest will not die, however, ovs-vswitchd will core (so guest network down). 2. Since this bug is only happening with specific QEMU packages (neither it will happen with old ones, nor the new ones), and if we are going to rebase to newer DPDK some day, the problem might solve itself too. So I would also have no problem to just put this bug aside at least for now. What do you think?
The plan is to rebase openvswitch-dpdk soon to 2.5, but we would still support 2.4 anyways. However, if you can't reproduce the issue with newer qemu then I would assume it's fixed somehow. This is the DPDK code: case VHOST_USER_RESET_OWNER: ops->reset_owner(ctx); break; This is the QEMU vhost-user spec: * VHOST_USER_RESET_OWNER Id: 4 Master payload: N/A This is no longer used. Used to be sent to request disabling all rings, but some clients interpreted it to also discard connection state (this interpretation would lead to bugs). It is recommended that clients either ignore this message, or use it to disable all rings. So maybe the newer qemu doesn't use it anymore. Having said that, I'd follow your suggestion in #2.
(In reply to Flavio Leitner from comment #8) > The plan is to rebase openvswitch-dpdk soon to 2.5, but we would still > support 2.4 anyways. However, if you can't reproduce the issue with newer > qemu then I would assume it's fixed somehow. > > This is the DPDK code: > case VHOST_USER_RESET_OWNER: > ops->reset_owner(ctx); > break; > > This is the QEMU vhost-user spec: > * VHOST_USER_RESET_OWNER > > Id: 4 > Master payload: N/A > > This is no longer used. Used to be sent to request disabling > all rings, but some clients interpreted it to also discard > connection state (this interpretation would lead to bugs). > It is recommended that clients either ignore this message, > or use it to disable all rings. > > So maybe the newer qemu doesn't use it anymore. > Having said that, I'd follow your suggestion in #2. Okay. Is there anything that I can provide (regarding to needinfo)? Peter
Closing with current release since the newer qemu fixes the issue.