[openstack-dev] [nova] using the qemu memory overhead in memory resource tracking or scheduling

Roman Podoliaka rpodolyaka at mirantis.com
Tue Sep 6 09:55:19 UTC 2016


Looks like we already have something like that in the virt drivers interface:

https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L205-L216

which is used in the resource tracker.

On Tue, Sep 6, 2016 at 10:40 AM, Balázs Gibizer
<balazs.gibizer at ericsson.com> wrote:
> Hi,
>
> In our cloud we use 1G huge pages for the instance memory.
> We started notice that qemu has a relevant memory overhead
> per domain (something like 300MB per domain). As we use
> huge pages for the instance memory nova scheduler makes
> placement decision based on the available huge pages.
> However in this situation the available host OS memory also
> needs to be considered. Reserving host OS memory deployment
> time is not practical as the needed reservation depends on the
> number of instances that will be run on that host.
>
> Is there any plan in the nova community to use qemu
> memory overhead in the placement decision in case of huge page
> backed instance?
>
> If there is no plan, do you support the idea adding such feature to nova?
>
> Cheers,
> gibi
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list