* [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported
@ 2020-07-08 11:38 Ryutaroh Matsumoto
2020-07-08 17:12 ` [Bug 1886811] " Laurent Vivier
` (15 more replies)
0 siblings, 16 replies; 17+ messages in thread
From: Ryutaroh Matsumoto @ 2020-07-08 11:38 UTC (permalink / raw)
To: qemu-devel
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
@ 2020-07-08 17:12 ` Laurent Vivier
2020-07-08 17:13 ` Ryutaroh Matsumoto
` (14 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Laurent Vivier @ 2020-07-08 17:12 UTC (permalink / raw)
To: qemu-devel
It would help to know which operation is not supported.
Could you get the coredump?
Is it possible to run the operation with "QEMU_STRACE" set in the environment?
Normally loop ioctls are supported.
But it seems the following ones are not implemented in QEMU:
LOOP_SET_CAPACITY, LOOP_SET_DIRECT_IO, LOOP_SET_BLOCK_SIZE.
** Tags added: linux-user
--
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
Status in qemu package in Debian:
Unknown
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
2020-07-08 17:12 ` [Bug 1886811] " Laurent Vivier
@ 2020-07-08 17:13 ` Ryutaroh Matsumoto
2020-07-08 19:39 ` Laurent Vivier
` (13 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Ryutaroh Matsumoto @ 2020-07-08 17:13 UTC (permalink / raw)
To: qemu-devel
** Bug watch added: Debian Bug tracker #964289
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964289
** Also affects: qemu (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964289
Importance: Unknown
Status: Unknown
--
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
Status in qemu package in Debian:
Unknown
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
2020-07-08 17:12 ` [Bug 1886811] " Laurent Vivier
2020-07-08 17:13 ` Ryutaroh Matsumoto
@ 2020-07-08 19:39 ` Laurent Vivier
2020-07-08 22:56 ` Ryutaroh Matsumoto
` (12 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Laurent Vivier @ 2020-07-08 19:39 UTC (permalink / raw)
To: qemu-devel
It seems systemd is trying to use RTM_SETLINK.
Could you try this patch:
diff --git a/linux-user/fd-trans.c b/linux-user/fd-trans.c
index c0687c52e62b..b09b5b7c13e0 100644
--- a/linux-user/fd-trans.c
+++ b/linux-user/fd-trans.c
@@ -1200,6 +1200,7 @@ static abi_long target_to_host_data_route(struct nlmsghdr *nlh)
break;
case RTM_NEWLINK:
case RTM_DELLINK:
+ case RTM_SETLINK:
if (nlh->nlmsg_len >= NLMSG_LENGTH(sizeof(*ifi))) {
ifi = NLMSG_DATA(nlh);
ifi->ifi_type = tswap16(ifi->ifi_type);
--
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
Status in qemu package in Debian:
Unknown
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
^ permalink raw reply related [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (2 preceding siblings ...)
2020-07-08 19:39 ` Laurent Vivier
@ 2020-07-08 22:56 ` Ryutaroh Matsumoto
2020-07-09 8:24 ` Laurent Vivier
` (11 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Ryutaroh Matsumoto @ 2020-07-08 22:56 UTC (permalink / raw)
To: qemu-devel
> It seems systemd is trying to use RTM_SETLINK.
> Could you try this patch:
Yes, you are right!
With the patch, I am able to boot containers of
Debian Bullseye of armhf and armel architectures!!
--
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
Status in qemu package in Debian:
Unknown
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (3 preceding siblings ...)
2020-07-08 22:56 ` Ryutaroh Matsumoto
@ 2020-07-09 8:24 ` Laurent Vivier
2020-07-09 13:33 ` Bug Watch Updater
` (10 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Laurent Vivier @ 2020-07-09 8:24 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: New => In Progress
** Changed in: qemu
Assignee: (unassigned) => Laurent Vivier (laurent-vivier)
--
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:
In Progress
Status in qemu package in Debian:
Unknown
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (4 preceding siblings ...)
2020-07-09 8:24 ` Laurent Vivier
@ 2020-07-09 13:33 ` Bug Watch Updater
2020-07-14 13:32 ` Ryutaroh Matsumoto
` (9 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Bug Watch Updater @ 2020-07-09 13:33 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu (Debian)
Status: Unknown => Confirmed
--
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:
In Progress
Status in qemu package in Debian:
Confirmed
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (5 preceding siblings ...)
2020-07-09 13:33 ` Bug Watch Updater
@ 2020-07-14 13:32 ` Ryutaroh Matsumoto
2020-07-15 4:18 ` Ryutaroh Matsumoto
` (8 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Ryutaroh Matsumoto @ 2020-07-14 13:32 UTC (permalink / raw)
To: qemu-devel
** Also affects: qemu (Ubuntu)
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:
In Progress
Status in qemu package in Ubuntu:
New
Status in qemu package in Debian:
Confirmed
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (6 preceding siblings ...)
2020-07-14 13:32 ` Ryutaroh Matsumoto
@ 2020-07-15 4:18 ` Ryutaroh Matsumoto
2020-07-15 6:36 ` Laurent Vivier
` (7 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Ryutaroh Matsumoto @ 2020-07-15 4:18 UTC (permalink / raw)
To: qemu-devel
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606
** No longer affects: qemu (Ubuntu)
** Also affects: qemu (Ubuntu)
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:
In Progress
Status in qemu package in Ubuntu:
New
Status in qemu package in Debian:
Confirmed
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (7 preceding siblings ...)
2020-07-15 4:18 ` Ryutaroh Matsumoto
@ 2020-07-15 6:36 ` Laurent Vivier
2020-07-21 7:37 ` Bug Watch Updater
` (6 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Laurent Vivier @ 2020-07-15 6:36 UTC (permalink / raw)
To: qemu-devel
Fixed here:
65b261a63a48 linux-user: add netlink RTM_SETLINK command
https://git.qemu.org/?p=qemu.git;a=commit;h=65b261a63a48fbb3b11193361d4ea0c38a3c3dfd
** Changed in: qemu
Status: In Progress => Fix Committed
--
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:
Fix Committed
Status in qemu package in Ubuntu:
New
Status in qemu package in Debian:
Confirmed
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (8 preceding siblings ...)
2020-07-15 6:36 ` Laurent Vivier
@ 2020-07-21 7:37 ` Bug Watch Updater
2020-07-31 14:19 ` Rafael David Tinoco
` (5 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Bug Watch Updater @ 2020-07-21 7:37 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu (Debian)
Status: Confirmed => Fix Released
--
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:
Fix Committed
Status in qemu package in Ubuntu:
New
Status in qemu package in Debian:
Fix Released
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (9 preceding siblings ...)
2020-07-21 7:37 ` Bug Watch Updater
@ 2020-07-31 14:19 ` Rafael David Tinoco
2020-08-12 6:14 ` Christian Ehrhardt
` (4 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Rafael David Tinoco @ 2020-07-31 14:19 UTC (permalink / raw)
To: qemu-devel
qemu (1:5.0-5ubuntu3) groovy; urgency=medium
has the merge with this fix:
- linux-user-add-netlink-RTM_SETLINK-command.patch (Closes: #964289)
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
--
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:
Fix Committed
Status in qemu package in Ubuntu:
Fix Released
Status in qemu package in Debian:
Fix Released
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (10 preceding siblings ...)
2020-07-31 14:19 ` Rafael David Tinoco
@ 2020-08-12 6:14 ` Christian Ehrhardt
2020-08-12 6:45 ` Christian Ehrhardt
` (3 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Christian Ehrhardt @ 2020-08-12 6:14 UTC (permalink / raw)
To: qemu-devel
** Also affects: qemu (Ubuntu Focal)
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:
Fix Committed
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Focal:
New
Status in qemu package in Debian:
Fix Released
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (11 preceding siblings ...)
2020-08-12 6:14 ` Christian Ehrhardt
@ 2020-08-12 6:45 ` Christian Ehrhardt
2020-08-19 5:44 ` Christian Ehrhardt
` (2 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: Christian Ehrhardt @ 2020-08-12 6:45 UTC (permalink / raw)
To: qemu-devel
@Ryutaroh - could you test [1] if it gets you around this bug (1886811)
and if bug 1890881 is present in focal as well?
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4197
--
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:
Fix Committed
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Focal:
New
Status in qemu package in Debian:
Fix Released
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (12 preceding siblings ...)
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
15 siblings, 0 replies; 17+ messages in thread
From: Christian Ehrhardt @ 2020-08-19 5:44 UTC (permalink / raw)
To: qemu-devel
To fully work this also needs the fix for bug 1890881 as identified
there.
** Changed in: qemu (Ubuntu Focal)
Status: New => Triaged
--
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:
Fix Committed
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Focal:
Triaged
Status in qemu package in Debian:
Fix Released
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (13 preceding siblings ...)
2020-08-19 5:44 ` Christian Ehrhardt
@ 2020-08-19 6:11 ` Christian Ehrhardt
2020-08-20 15:35 ` Thomas Huth
15 siblings, 0 replies; 17+ messages in thread
From: Christian Ehrhardt @ 2020-08-19 6:11 UTC (permalink / raw)
To: qemu-devel
SRU need the bug 1890881 fix to be really helpful, but the dependency chain of that is not SRUable.
See: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/comments/17
Users (of this valid but rare use case) can either use Groovy which will
fix this or wait until Openstack Victoria will make it available for
Focal via the Ubuntu Cloud Archive [1].
[1]: https://wiki.ubuntu.com/OpenStack/CloudArchive
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => Won't Fix
--
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:
Fix Committed
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Focal:
Won't Fix
Status in qemu package in Debian:
Fix Released
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
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
` (14 preceding siblings ...)
2020-08-19 6:11 ` Christian Ehrhardt
@ 2020-08-20 15:35 ` Thomas Huth
15 siblings, 0 replies; 17+ messages in thread
From: Thomas Huth @ 2020-08-20 15:35 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Focal:
Won't Fix
Status in qemu package in Debian:
Fix Released
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
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2020-08-20 15:42 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-08 11:38 [Bug 1886811] [NEW] systemd complains Failed to enqueue loopback interface start request: Operation not supported Ryutaroh Matsumoto
2020-07-08 17:12 ` [Bug 1886811] " 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
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.