** Description changed: - Although aarch64 supports spawning a vm with hugepages, in nova code, - the libvirt driver considers only x86_64 and I686. Both for NUMA and - Hugepage support, AARCH64 needs to be added. Due to this bug, vm can not - be launched with hugepage using OpenStack on aarch64 servers. + [Impact] + Although aarch64 supports spawning a vm with hugepages, in nova code, the libvirt driver considers only x86_64 and I686. Both for NUMA and Hugepage support, AARCH64 needs to be added. Due to this bug, vm can not be launched with hugepage using OpenStack on aarch64 servers. + [Test Case] Steps to reproduce: On an openstack environment running on aarch64: 1. Configure compute to use hugepages. 2. Set mem_page_size="2048" for a flavor - 3. Launch a VM using the above flavor. + 3. Launch a VM using the above flavor. Expected result: - VM should be launched with hugepages and the libvirt xml should have + VM should be launched with hugepages and the libvirt xml should have - <memoryBacking> - <hugepages> - <page size='2048' unit='KiB' nodeset='0'/> - </hugepages> - </memoryBacking> + <memoryBacking> + <hugepages> + <page size='2048' unit='KiB' nodeset='0'/> + </hugepages> + </memoryBacking> Actual result: VM is launched without hugepages. There are no error logs in nova-scheduler. + + [Regression Risk] + Risk is minimized by the fact that this change is just enabling the same code for arm64 that is already enabled for the i386, amd64 and ppc64el Ubuntu architectures.
** Description changed: [Impact] Although aarch64 supports spawning a vm with hugepages, in nova code, the libvirt driver considers only x86_64 and I686. Both for NUMA and Hugepage support, AARCH64 needs to be added. Due to this bug, vm can not be launched with hugepage using OpenStack on aarch64 servers. [Test Case] Steps to reproduce: On an openstack environment running on aarch64: 1. Configure compute to use hugepages. 2. Set mem_page_size="2048" for a flavor 3. Launch a VM using the above flavor. Expected result: VM should be launched with hugepages and the libvirt xml should have <memoryBacking> <hugepages> <page size='2048' unit='KiB' nodeset='0'/> </hugepages> </memoryBacking> Actual result: VM is launched without hugepages. There are no error logs in nova-scheduler. [Regression Risk] - Risk is minimized by the fact that this change is just enabling the same code for arm64 that is already enabled for the i386, amd64 and ppc64el Ubuntu architectures. + Risk is minimized by the fact that this change is just enabling the same code for arm64 that is already enabled for Ubuntu/x86. ** Patch added: "lp1623871-y.patch" https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1623871/+attachment/4749709/+files/lp1623871-y.patch ** Description changed: [Impact] Although aarch64 supports spawning a vm with hugepages, in nova code, the libvirt driver considers only x86_64 and I686. Both for NUMA and Hugepage support, AARCH64 needs to be added. Due to this bug, vm can not be launched with hugepage using OpenStack on aarch64 servers. + + Note: this depends on the fix for LP: #1627926. [Test Case] Steps to reproduce: On an openstack environment running on aarch64: 1. Configure compute to use hugepages. 2. Set mem_page_size="2048" for a flavor 3. Launch a VM using the above flavor. Expected result: VM should be launched with hugepages and the libvirt xml should have <memoryBacking> <hugepages> <page size='2048' unit='KiB' nodeset='0'/> </hugepages> </memoryBacking> Actual result: VM is launched without hugepages. There are no error logs in nova-scheduler. [Regression Risk] Risk is minimized by the fact that this change is just enabling the same code for arm64 that is already enabled for Ubuntu/x86. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623871 Title: Nova hugepage support does not include aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1623871/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
