← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1623871] Re: Nova hugepage support does not include aarch64

 

Thanks for proposing to add aarch64 support to hugepages and NUMA
instances.

Considering the operator impact and the fact that we would need to
verify the libvirt and qemu minimum versions that we ship for making
sure they support the above, I think it is really important to have that
specific feature request to be handled accordingly with people able to
review your proposal.

In Nova, we follow a specific process for writing new specifications and
proposals that you can find more information on
http://docs.openstack.org/developer/nova/process.html#how-do-i-get-my-
code-merged

Basically, it requires you to write a blueprint and discuss on IRC to
see whether your blueprint needs a formal specification writing called a
"spec" file.


** Changed in: nova
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1623871

Title:
  Nova hugepage support does not include aarch64

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  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.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1623871/+subscriptions


References