Hi Elio, ovs-dpdk testing needs to be done on hardware. Virtual environments will be using ovs only moving forward. The code required to allow this was merged earlier today. More details will be sent shortly. https://review.openstack.org/#/c/633924/ Using OVS in a virtual env is required because master neutron doesn’t support ovs-dpdk in virtual environments. We have been carrying an stx specific patch to allow users to continue working on virtual env. But with the above code now merging, this patch will be discarded once the above feature is sufficiently tested. Hope this clarifies things. Thanks, Ghada From: Martinez Monroy, Elio [mailto:elio.martinez.monroy@intel.com] Sent: Wednesday, March 27, 2019 3:36 PM To: Peters, Matt; Xu, Chenjie; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss@lists.starlingx.io'; Zhao, Forrest; Rowsell, Brent Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing So, in order to develop our NUMA test cases, we should configure that topology in our VM’s? How can we do it? Do you have the steps? BR Elio From: Peters, Matt [mailto:Matt.Peters@windriver.com] Sent: Wednesday, March 27, 2019 1:19 PM To: Martinez Monroy, Elio <elio.martinez.monroy@intel.com<mailto:elio.martinez.monroy@intel.com>>; Xu, Chenjie <chenjie.xu@intel.com<mailto:chenjie.xu@intel.com>>; Khalil, Ghada <Ghada.Khalil@windriver.com<mailto:Ghada.Khalil@windriver.com>>; Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; Cabrales, Ada <ada.cabrales@intel.com<mailto:ada.cabrales@intel.com>>; Perez, Ricardo O <ricardo.o.perez@intel.com<mailto:ricardo.o.perez@intel.com>> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>; Zhao, Forrest <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>>; Rowsell, Brent <Brent.Rowsell@windriver.com<mailto:Brent.Rowsell@windriver.com>> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, From the output below, this data is taken from a virtual system. In a QEMU/KVM environment, it is not expected to have a NUMA topology unless it has been explicitly configured in the domain configuration of the emulated host. I’m assuming the tests being performed by Chenjie are in a HW lab. This can be confirmed by providing the same set of data for those test systems. Thanks, Matt From: "Martinez Monroy, Elio" <elio.martinez.monroy@intel.com<mailto:elio.martinez.monroy@intel.com>> Date: Wednesday, March 27, 2019 at 2:47 PM To: "Peters, Matt" <Matt.Peters@windriver.com<mailto:Matt.Peters@windriver.com>>, "Xu, Chenjie" <chenjie.xu@intel.com<mailto:chenjie.xu@intel.com>>, Ghada Khalil <Ghada.Khalil@windriver.com<mailto:Ghada.Khalil@windriver.com>>, "Lin, Shuicheng" <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>, "Cabrales, Ada" <ada.cabrales@intel.com<mailto:ada.cabrales@intel.com>>, "Perez, Ricardo O" <ricardo.o.perez@intel.com<mailto:ricardo.o.perez@intel.com>> Cc: "'starlingx-discuss@lists.starlingx.io'" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>, "Zhao, Forrest" <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>>, Brent Rowsell <Brent.Rowsell@windriver.com<mailto:Brent.Rowsell@windriver.com>> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters@windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie <chenjie.xu@intel.com<mailto:chenjie.xu@intel.com>>; Khalil, Ghada <Ghada.Khalil@windriver.com<mailto:Ghada.Khalil@windriver.com>>; Martinez Monroy, Elio <elio.martinez.monroy@intel.com<mailto:elio.martinez.monroy@intel.com>>; Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; Cabrales, Ada <ada.cabrales@intel.com<mailto:ada.cabrales@intel.com>>; Perez, Ricardo O <ricardo.o.perez@intel.com<mailto:ricardo.o.perez@intel.com>> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>; Zhao, Forrest <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>>; Rowsell, Brent <Brent.Rowsell@windriver.com<mailto:Brent.Rowsell@windriver.com>> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" <chenjie.xu@intel.com<mailto:chenjie.xu@intel.com>> Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" <Matt.Peters@windriver.com<mailto:Matt.Peters@windriver.com>>, Ghada Khalil <Ghada.Khalil@windriver.com<mailto:Ghada.Khalil@windriver.com>>, "Martinez Monroy, Elio" <elio.martinez.monroy@intel.com<mailto:elio.martinez.monroy@intel.com>>, "Lin, Shuicheng" <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>, "Cabrales, Ada" <ada.cabrales@intel.com<mailto:ada.cabrales@intel.com>>, "Perez, Ricardo O" <ricardo.o.perez@intel.com<mailto:ricardo.o.perez@intel.com>> Cc: "'starlingx-discuss@lists.starlingx.io'" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>, "Zhao, Forrest" <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174... Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' <Matt.Peters@windriver.com<mailto:Matt.Peters@windriver.com>>; Khalil, Ghada <Ghada.Khalil@windriver.com<mailto:Ghada.Khalil@windriver.com>>; Martinez Monroy, Elio <elio.martinez.monroy@intel.com<mailto:elio.martinez.monroy@intel.com>>; Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; Cabrales, Ada <ada.cabrales@intel.com<mailto:ada.cabrales@intel.com>>; Perez, Ricardo O <ricardo.o.perez@intel.com<mailto:ricardo.o.perez@intel.com>> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>; Zhao, Forrest <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie