On 5/11/20 9:24 PM, Igor Mammedov wrote:
On Mon, 11 May 2020 18:00:01 +0200
Philippe Mathieu-Daudé wrote:
Hi Eduardo,
On 5/4/20 5:44 PM, Eduardo Habkost wrote:
On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
T
On Mon, 11 May 2020 18:00:01 +0200
Philippe Mathieu-Daudé wrote:
> Hi Eduardo,
>
> On 5/4/20 5:44 PM, Eduardo Habkost wrote:
> > On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
> >> Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
> >> The backend however calls
Hi Eduardo,
On 5/4/20 5:44 PM, Eduardo Habkost wrote:
On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
The backend however calls mbind() which is typically NOP
in case of default policy/absent host-nodes bitmap.
Ho
On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
> Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
> The backend however calls mbind() which is typically NOP
> in case of default policy/absent host-nodes bitmap.
> However when runing in container with black-listed m
On 5/1/20 10:57 AM, Daniel P. Berrangé wrote:
On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
The backend however calls mbind() which is typically NOP
in case of default policy/absent host-nodes bitmap.
However whe
On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
> Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
> The backend however calls mbind() which is typically NOP
> in case of default policy/absent host-nodes bitmap.
> However when runing in container with black-listed m
Thanks! I applied the patch, and now it works also inside the docker container,
for all architectures (i386, x86_64, arm, aarch64) for which I have test cases
at hand.
Indeed, since the container is configured by a public cloud service, there is
no possibility to change any security settings.
Typo "empty" in patch subject.
On 4/30/20 5:46 PM, Igor Mammedov wrote:
Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
The backend however calls mbind() which is typically NOP
in case of default policy/absent host-nodes bitmap.
However when runing in container with black-list
Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
The backend however calls mbind() which is typically NOP
in case of default policy/absent host-nodes bitmap.
However when runing in container with black-listed mbind()
syscall, QEMU fails to start with error
"cannot bind memory to
