qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <Laurent@vivier.eu>
To: qemu-devel@nongnu.org
Subject: [Bug 1857811] Re: qemu user static binary seems to lack support for network namespace.
Date: Thu, 02 Jan 2020 11:57:19 -0000	[thread overview]
Message-ID: <157796623995.28078.2105039412334429490.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 157762661516.5433.16221584605990009162.malonedeb@gac.canonical.com

Could you run qemu unimplemented error trace, by using "export
QEMU_LOG=unimp"?

You can also set the QEMU_STRACE="" to see which syscall fails.

-- 
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 namespace.

Status in QEMU:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1857811/+subscriptions


  reply	other threads:[~2020-01-02 12:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-29 13:36 [Bug 1857811] [NEW] qemu user static binary seems to lack support for network namespace crocket
2020-01-02 11:57 ` Laurent Vivier [this message]
2020-01-02 13:51 ` [Bug 1857811] " crocket
2020-02-12 12:10 ` Laurent Vivier
2020-02-12 12:45 ` crocket
2020-02-12 12:47 ` crocket
2020-02-12 18:32 ` Laurent Vivier
2020-02-12 22:47 ` crocket
2020-02-20 12:27 ` Laurent Vivier
2020-02-20 14:07 ` crocket
2020-02-20 14:13 ` Laurent Vivier
2020-02-21  7:22 ` crocket
2020-02-21  9:58 ` Laurent Vivier

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=157796623995.28078.2105039412334429490.malone@chaenomeles.canonical.com \
    --to=laurent@vivier.eu \
    --cc=1857811@bugs.launchpad.net \
    --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).