Thanks Chenjie for confirming. I added the following note in the container installation guide[0]: IMPORTANT: When deploying OVS-DPDK, VMs must be configured to use a flavor with property: hw:mem_page_size=large [0] https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Configure_... Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu@intel.com] Sent: Monday, April 08, 2019 3:39 AM To: Peters, Matt; Liu, ZhipengS; He, Yongli; Friesen, Chris Cc: 'starlingx-discuss@lists.starlingx.io'; Khalil, Ghada; Zhao, Forrest; Rowsell, Brent; Gauld, James; Le, Huifeng; Martinez Monroy, Elio; Perez, Ricardo O; Cabrales, Ada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, After setting property "hw:mem_page_size=large" to flavor, the newly created VM can get IP from DHCP and ping other VM successfully. And NUMA related sections exist in the domain XML file (new domain XML mem_page_size.xml is attached). My steps are listed in the bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 I think it’s better to modify the installation guide to include how to create VM on different environment (OVS/OVSDPDK). Please let me know your idea. Best Regards Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters@windriver.com] Sent: Thursday, April 4, 2019 3:21 AM To: Xu, Chenjie <chenjie.xu@intel.com<mailto:chenjie.xu@intel.com>>; Liu, ZhipengS <zhipengs.liu@intel.com<mailto:zhipengs.liu@intel.com>>; He, Yongli <yongli.he@intel.com<mailto:yongli.he@intel.com>> Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>; Khalil, Ghada <Ghada.Khalil@windriver.com<mailto:Ghada.Khalil@windriver.com>>; Zhao, Forrest <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>>; Rowsell, Brent <Brent.Rowsell@windriver.com<mailto:Brent.Rowsell@windriver.com>>; Gauld, James <James.Gauld@windriver.com<mailto:James.Gauld@windriver.com>>; Le, Huifeng <huifeng.le@intel.com<mailto:huifeng.le@intel.com>>; Martinez Monroy, Elio <elio.martinez.monroy@intel.com<mailto:elio.martinez.monroy@intel.com>>; Perez, Ricardo O <ricardo.o.perez@intel.com<mailto:ricardo.o.perez@intel.com>>; Cabrales, Ada <ada.cabrales@intel.com<mailto:ada.cabrales@intel.com>>; Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Folks, Thanks to Chris Friesen for point this out, but we believe the issues you are experiencing is due to the requirement for guests to be backed by huge pages to operate with OVS-DPDK vhost-user based ports/interfaces. The master (default) behavior for the latest nova will default to 4K pages for the guest, but this is not compatible with OVS-DPDK. The guests must be configured to use a flavor that has the property hw:mem_page_size=large set. You can follow this link to read more about the requirements on the guests for OVS-DPDK: https://docs.openstack.org/neutron/rocky/admin/config-ovs-dpdk.html “vhost-user requires file descriptor-backed shared memory. Currently, the only way to request this is by requesting large pages. This is why instances spawned on hosts with OVS-DPDK must request large pages”. Hope this helps. -Matt