On 7/19/24 14:35, Phelan, Michael wrote: > >> -----Original Message----- >> From: Ilya Maximets <[email protected]> >> Sent: Thursday, July 18, 2024 9:09 PM >> To: Phelan, Michael <[email protected]> >> Cc: [email protected]; ovs-dev <[email protected]> >> Subject: Re: [ovs-build] |fail| pw1960612 [ovs-dev,2/2] Prepare for post- >> 3.4.0 (3.4.90). >> >> On 7/17/24 17:31, Phelan, Michael wrote: >>> >>>> -----Original Message----- >>>> From: Ilya Maximets <[email protected]> >>>> Sent: Wednesday, July 17, 2024 10:43 AM >>>> To: Phelan, Michael <[email protected]> >>>> Cc: [email protected]; ovs-dev <[email protected]> >>>> Subject: Re: [ovs-build] |fail| pw1960612 [ovs-dev,2/2] Prepare for >>>> post- >>>> 3.4.0 (3.4.90). >>>> >>>> On 7/17/24 10:36, Phelan, Michael wrote: >>>>> >>>>>> -----Original Message----- >>>>>> From: Ilya Maximets <[email protected]> >>>>>> Sent: Tuesday, July 16, 2024 12:25 PM >>>>>> To: Phelan, Michael <[email protected]> >>>>>> Cc: [email protected]; ovs-dev <[email protected]> >>>>>> Subject: Re: [ovs-build] |fail| pw1960612 [ovs-dev,2/2] Prepare for >>>>>> post- >>>>>> 3.4.0 (3.4.90). >>>>>> >>>>>> On 7/15/24 22:23, [email protected] wrote: >>>>>>> Test-Label: intel-ovs-compilation >>>>>>> Test-Status: fail >>>>>>> http://patchwork.ozlabs.org/api/patches/1960612/ >>>>>>> >> >> <snip> >> >>>>> Device "tap0" does not exist. >>>>> Device "tap0" does not exist. >>>>> system-dpdk.at:123: wait failed after 30 seconds >>>>> ./ovs-macros.at:242: hard failure >>>>> /root/ovs-dev/tests/system-dpdk-testsuite.dir/004/cleanup: line 1: >>>>> kill: (155084) - No such process 4. system-dpdk.at:102: 4. OVS-DPDK >>>>> - ping vhost-user ports (system-dpdk.at:102): FAILED >>>>> (ovs-macros.at:242) >>>>> >>>>> Do you see an obvious problem here? >>>> >>>> Looks like testpmd wasn't able to create the tap0 interface. >>>> Are there any errors in testpmd.log ? >>> >>> The ouput in the testpmd.log is: >>> >>> EAL: Detected 96 lcore(s) >>> EAL: Detected 2 NUMA nodes >>> EAL: Selected IOVA mode 'VA' >>> EAL: Probing VFIO support... >>> EAL: VFIO support initialized >>> EAL: No legacy callbacks, legacy socket not created Auto-start >>> selected >>> Warning: NUMA should be configured manually by using --port-numa- >> config and --ring-numa-config parameters along with --numa. >>> testpmd: create a new mbuf pool <mb_pool_0>: n=907456, size=2176, >>> socket=0 >>> testpmd: preferred mempool ops selected: ring_mp_mc >>> EAL: Error - exiting with code: 1 >>> Cause: Creation of mbuf pool for socket 0 failed: Cannot allocate >>> memory >> >> Are there enough hugepages allocated on the node? > > There was 2 gigs of Hugepages allocated on both nodes, I have increased it > to 4 gigs and the test is passing now.
Thanks, Michael. I wonder why the requirements changed... I no longer see these failures in reports, however we started to get strange compilation failures while there are no actual errors in the reported build log: https://mail.openvswitch.org/pipermail/ovs-build/2024-July/040392.html Could you take a look at these too? Best regards, Ilya Maximets. >> >> Could you try to manually start testpmd on this machine by using command >> line arguments from testpmd.cmd file from the test? >> >>> >>>> >>>>>> >>>>>>> 2024-07-15T19:14:11Z|00007|dpdk|INFO|Using DPDK 23.11.0 >>>>>> >>>>>> I remember that there were some vhost issues in 23.11.0, we may >>>>>> need to upgrade to 23.11.1 here. We use it in GitHub Actions as well. >>>>> >>>>> We can upgrade to 23.11.1 no problem if it we need to. >>>> >>>> I think we should do that, since that's the version we officially >>>> recommend now. >>> Sure, I'll do that now. >>>> >>>>> >>>>> Thanks, >>>>> Michael. >>>>>> >>>>>> Best regards, Ilya Maximets. >>> > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
