[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** 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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
@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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** 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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** 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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** 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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** 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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** 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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
> 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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
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
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** 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
