I just called _configure_loopback_interface in a qemu-aarch64 chroot,
and the error is not reproducible with qemu-4.2.0. Has it been fixed?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1857811
Can you rephrase your question? I don't know what to do with your
question.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1857811
Title:
qemu user static binary seems to lack support for network
qemu-4.0.0
> uname -a
Linux gentoo 4.19.97-gentoo #3 SMP PREEMPT Mon Feb 10 15:09:44 KST 2020 x86_64
AMD FX(tm)-8300 Eight-Core Processor AuthenticAMD GNU/Linux
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
def _configure_loopback_interface():
"""
Configure the loopback interface.
"""
# We add some additional addresses to work around odd behavior in
glibc's
# getaddrinfo() implementation when the AI_ADDRCONFIG flag is set.
#
# For example:
You can obtain portage source code from
https://gentoo.osuosl.org/distfiles/portage-2.3.84.tar.bz2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1857811
Title:
qemu user static binary seems to
I think you should investigate
`qemu: qemu_thread_create: Invalid argument`
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1829459
Title:
qemu seems to lack support for pid namespace.
Status in
I executed "emerge" with QEMU_LOG=unimp and QEMU_STRACE="".
** Attachment added: "emerge.log"
https://bugs.launchpad.net/qemu/+bug/1857811/+attachment/5317106/+files/emerge.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
In a native chroot, `sudo unshare --pid -- echo hello world` works
without a problem.
In a qemu-aarch64 chroot, `sudo unshare --keep-caps --pid -- echo hello
world` fails with the same error described in this issue.
`qemu: qemu_thread_create: Invalid argument`
--
You received this bug
According to `man unshare`, --keep-caps seems to apply only to user
namespace.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1829459
Title:
qemu seems to lack support for pid namespace.
Status in
Public bug reported:
Whenever I execute emerge in gentoo linux in qemu-aarch64 chroot, I see
the following error message.
Unable to configure loopback interface: Operation not supported
If I disable emerge's network-sandbox which utilizes network namespace,
the error disappears.
** Affects:
** Summary changed:
- qemu: qemu_thread_create: Invalid argument
+ qemu seems to lack support for pid namespace.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1829459
Title:
qemu seems to lack
Public bug reported:
# Version
qemu-4.0.0
glibc-2.28
# commands used to launch qemu-aarch64 in user mode.
: ${QEMU_BINFMT_FLAGS:=OC}
printf '%s\n' ':qemu-
12 matches
Mail list logo
