Re: [libvirt] [PATCH v2 2/2] qemu: Set up EMULATOR thread and cpuset.mems before exec()-ing qemu

2019-04-16 Thread Martin Kletzander
On Mon, Apr 15, 2019 at 06:32:32PM +0200, Michal Privoznik wrote: On 4/15/19 3:47 PM, Martin Kletzander wrote: On Wed, Apr 10, 2019 at 06:10:44PM +0200, Michal Privoznik wrote: It's funny how this went unnoticed for such a long time. Long story short, if a domain is configured with

Re: [libvirt] [PATCH v2 2/2] qemu: Set up EMULATOR thread and cpuset.mems before exec()-ing qemu

2019-04-15 Thread Michal Privoznik
On 4/15/19 3:47 PM, Martin Kletzander wrote: On Wed, Apr 10, 2019 at 06:10:44PM +0200, Michal Privoznik wrote: It's funny how this went unnoticed for such a long time. Long story short, if a domain is configured with VIR_DOMAIN_NUMATUNE_MEM_STRICT libvirt doesn't really honour that. This is

Re: [libvirt] [PATCH v2 2/2] qemu: Set up EMULATOR thread and cpuset.mems before exec()-ing qemu

2019-04-15 Thread Martin Kletzander
On Wed, Apr 10, 2019 at 06:10:44PM +0200, Michal Privoznik wrote: It's funny how this went unnoticed for such a long time. Long story short, if a domain is configured with VIR_DOMAIN_NUMATUNE_MEM_STRICT libvirt doesn't really honour that. This is because of 7e72ac787848 after which libvirt

[libvirt] [PATCH v2 2/2] qemu: Set up EMULATOR thread and cpuset.mems before exec()-ing qemu

2019-04-10 Thread Michal Privoznik
It's funny how this went unnoticed for such a long time. Long story short, if a domain is configured with VIR_DOMAIN_NUMATUNE_MEM_STRICT libvirt doesn't really honour that. This is because of 7e72ac787848 after which libvirt allowed qemu to allocate memory just anywhere and only after that it used