Hi all, I'm having an issue with virtio devices in a VM on OCI when setting up multiple workers with VPP (21.06). I'm looking for some suggestions on where to start the debugging. Here is what I'm seeing:
* With the startup configuration commenting out "corelist-workers 2" (so that there are no workers), everything works correctly. * Same setup with one change, uncomment "corelist-workers 2", ip4 gets disabled. I get the following dispatch traces in the event-logger: 000:00:00:002:662 workers 1 dpdk-input-return: 2 000:00:00:002:667 workers 1 ethernet-input-call: 2 000:00:00:002:690 workers 1 ethernet-input-return: 2 000:00:00:002:692 workers 1 ip4-input-call: 2 000:00:00:002:698 workers 1 ip4-input-return: 2 000:00:00:002:699 workers 1 ip4-not-enabled-call: 2 000:00:00:002:705 workers 1 ip4-not-enabled-return: 2 000:00:00:002:705 workers 1 error-drop-call: 2 000:00:00:002:707 workers 1 error-drop-return: 2 When using a VM on openstack, I don't have this problem. Something specific about the OCI setup seems to be causing issues. I also don't have issues on OCI when using the Broadcom and Mellanox virtual functions with multiple workers. Only with virtio (PARAVIRTUALIZED). Any suggestions on what is resulting in the ip4 disablement? Any suggestions on where to start the debug? I can get GDB out and step through it, but was hoping for someone to zero me on something if possible. Thanks, Scott McMillan
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20786): https://lists.fd.io/g/vpp-dev/message/20786 Mute This Topic: https://lists.fd.io/mt/88683738/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
