From: Ryutaroh Matsumoto <1886811@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported
Date: Wed, 08 Jul 2020 11:38:29 -0000 [thread overview]
Message-ID: <159420830935.32230.13858618076699173558.malonedeb@gac.canonical.com> (raw)
Public bug reported:
This symptom seems similar to
https://bugs.launchpad.net/qemu/+bug/1823790
Host Linux: Debian 11 Bullseye (testing) on x84-64 architecture
qemu version: latest git of git commit hash eb2c66b10efd2b914b56b20ae90655914310c925
compiled with "./configure --static --disable-system"
Down stream bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964289
Bug report (closed) to systemd: https://github.com/systemd/systemd/issues/16359
systemd in armhf and armel (both little endian 32-bit) containers fail to start with
Failed to enqueue loopback interface start request: Operation not supported
How to reproduce on Debian (and probably Ubuntu):
mmdebstrap --components="main contrib non-free" --architectures=armhf --variant=important bullseye /var/lib/machines/armhf-bullseye
systemd-nspawn -D /var/lib/machines/armhf-bullseye -b
When "armhf" architecture is replaced with "mips" (32-bit big endian) or "ppc64"
(64-bit big endian), the container starts up fine.
The same symptom is also observed with "powerpc" (32-bit big endian)
architecture.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1886811
Title:
systemd complains Failed to enqueue loopback interface start request:
Operation not supported
Status in QEMU:
New
Bug description:
This symptom seems similar to
https://bugs.launchpad.net/qemu/+bug/1823790
Host Linux: Debian 11 Bullseye (testing) on x84-64 architecture
qemu version: latest git of git commit hash eb2c66b10efd2b914b56b20ae90655914310c925
compiled with "./configure --static --disable-system"
Down stream bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964289
Bug report (closed) to systemd: https://github.com/systemd/systemd/issues/16359
systemd in armhf and armel (both little endian 32-bit) containers fail to start with
Failed to enqueue loopback interface start request: Operation not supported
How to reproduce on Debian (and probably Ubuntu):
mmdebstrap --components="main contrib non-free" --architectures=armhf --variant=important bullseye /var/lib/machines/armhf-bullseye
systemd-nspawn -D /var/lib/machines/armhf-bullseye -b
When "armhf" architecture is replaced with "mips" (32-bit big endian) or "ppc64"
(64-bit big endian), the container starts up fine.
The same symptom is also observed with "powerpc" (32-bit big endian)
architecture.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1886811/+subscriptions
next reply other threads:[~2020-07-08 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 11:38 Ryutaroh Matsumoto [this message]
2020-07-08 17:12 ` [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported Laurent Vivier
2020-07-08 17:13 ` Ryutaroh Matsumoto
2020-07-08 19:39 ` Laurent Vivier
2020-07-08 22:56 ` Ryutaroh Matsumoto
2020-07-09 8:24 ` Laurent Vivier
2020-07-09 13:33 ` Bug Watch Updater
2020-07-14 13:32 ` Ryutaroh Matsumoto
2020-07-15 4:18 ` Ryutaroh Matsumoto
2020-07-15 6:36 ` Laurent Vivier
2020-07-21 7:37 ` Bug Watch Updater
2020-07-31 14:19 ` Rafael David Tinoco
2020-08-12 6:14 ` Christian Ehrhardt
2020-08-12 6:45 ` Christian Ehrhardt
2020-08-19 5:44 ` Christian Ehrhardt
2020-08-19 6:11 ` Christian Ehrhardt
2020-08-20 15:35 ` Thomas Huth
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=159420830935.32230.13858618076699173558.malonedeb@gac.canonical.com \
--to=1886811@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.