From: Manuel Hohmann <mhohmann@physnet.uni-hamburg.de>
To: qemu-devel@nongnu.org
Cc: imammedo@redhat.com
Subject: Error "cannot bind memory to host NUMA nodes: Operation not permitted" running inside docker
Date: Wed, 29 Apr 2020 23:40:32 +0300 [thread overview]
Message-ID: <76d8eb61-e89e-0465-974b-6901a5fb848e@physnet.uni-hamburg.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1844 bytes --]
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 line):
qemu-system-i386 -m 64 -M pc -smp 1 -display none -monitor stdio -drive file=mp-acpi/NOS.iso,media=cdrom,id=d -boot order=d -d cpu_reset
The docker image which shows the error is available here:
https://hub.docker.com/repository/docker/xenos1984/test-qemu
Built on Ubuntu 20.04, and including NUMA support with libnuma-dev package installed, from the following sources:
https://github.com/xenos1984/cross-toolchain/tree/master/tools-qemu
https://github.com/xenos1984/cross-toolchain/tree/master/test-qemu
The iso image used can be obtained here, but should not be relevant:
https://github.com/xenos1984/NOS/releases/download/latest/nos-i686.iso.bz2
The command fails when the image is used in a CI environment:
https://circleci.com/gh/xenos1984/NOS/953
On recommendation by @imammedo I post the issue to qemu-devel, and also tried the following patch:
--- a/backends/hostmem.c
+++ b/backends/hostmem.c
@@ -384,3 +384,3 @@
if (mbind(ptr, sz, backend->policy,
- maxnode ? backend->host_nodes : NULL, maxnode + 1, flags)) {
+ maxnode ? backend->host_nodes : NULL, 0, flags)) {
if (backend->policy != MPOL_DEFAULT || errno != ENOSYS) {
But no success, the same error occurs. It happens only within docker - the same command runs fine on my desktop (also Ubuntu 20.04) system.
Best regards,
xenos1984 / Manuel Hohmann
PS: I apologize if this mail is sent / received more than once; there was a problem with my outgoing mails.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-29 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 20:40 Manuel Hohmann [this message]
2020-04-30 8:52 ` Error "cannot bind memory to host NUMA nodes: Operation not permitted" running inside docker Daniel P. Berrangé
2020-04-30 11:45 ` Igor Mammedov
2020-04-30 11:49 ` Daniel P. Berrangé
-- strict thread matches above, loose matches on Subject: below --
2020-04-29 19:09 Manuel Hohmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76d8eb61-e89e-0465-974b-6901a5fb848e@physnet.uni-hamburg.de \
--to=mhohmann@physnet.uni-hamburg.de \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).