systemd complains Failed to enqueue loopback interface start request: Operation not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Laurent Vivier | ||
qemu (Debian) |
Fix Released
|
Unknown
|
|||
qemu (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
This symptom seems similar to
https:/
Host Linux: Debian 11 Bullseye (testing) on x84-64 architecture
qemu version: latest git of git commit hash eb2c66b10efd2b9
compiled with "./configure --static --disable-system"
Down stream bug report at https:/
Bug report (closed) to systemd: https:/
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
systemd-nspawn -D /var/lib/
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.
Changed in qemu: | |
status: | New → In Progress |
assignee: | nobody → Laurent Vivier (laurent-vivier) |
Changed in qemu (Debian): | |
status: | Unknown → Confirmed |
Changed in qemu (Debian): | |
status: | Confirmed → Fix Released |
Changed in qemu: | |
status: | Fix Committed → Fix Released |
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.