Re: Error "cannot bind memory to host NUMA nodes: Operation not permitted" running inside docker

2020-04-30 Thread Daniel P . Berrangé
On Thu, Apr 30, 2020 at 01:45:58PM +0200, Igor Mammedov wrote: > On Thu, 30 Apr 2020 09:52:15 +0100 > Daniel P. Berrangé wrote: > > > On Wed, Apr 29, 2020 at 11:40:32PM +0300, Manuel Hohmann wrote: > > > Hi, > > > > > > I encountered the following error message on the QEMU 5.0.0 release, > > >

Re: Error "cannot bind memory to host NUMA nodes: Operation not permitted" running inside docker

2020-04-30 Thread Igor Mammedov
On Thu, 30 Apr 2020 09:52:15 +0100 Daniel P. Berrangé wrote: > On Wed, Apr 29, 2020 at 11:40:32PM +0300, Manuel Hohmann wrote: > > Hi, > > > > I encountered the following error message on the QEMU 5.0.0 release, > > compiled and run inside a docker image: > > > > "cannot bind memory to host NU

Re: Error "cannot bind memory to host NUMA nodes: Operation not permitted" running inside docker

2020-04-30 Thread Daniel P . Berrangé
On Wed, Apr 29, 2020 at 11:40:32PM +0300, Manuel Hohmann wrote: > Hi, > > I encountered the following error message on the QEMU 5.0.0 release, compiled > and run inside a docker image: > > "cannot bind memory to host NUMA nodes: Operation not permitted" The error is reporting that mbind() faile

Error "cannot bind memory to host NUMA nodes: Operation not permitted" running inside docker

2020-04-29 Thread Manuel Hohmann
Hi, I encountered the following error on the QEMU 5.0.0 release, compiled and run inside a docker image: "cannot bind memory to host NUMA nodes: Operation not permitted" The QEMU command line to reproduce this behavior: qemu-system-i386 -m 64 -M pc -smp 1 -display none -monitor stdio -drive

Error "cannot bind memory to host NUMA nodes: Operation not permitted" running inside docker

2020-04-29 Thread Manuel Hohmann
Hi, I encountered the following error message on the QEMU 5.0.0 release, compiled and run inside a docker image: "cannot bind memory to host NUMA nodes: Operation not permitted" The QEMU command line to reproduce this behavior (it happens also on -x86_64, -arm, -aarch64 with similar command l