Setup to reproduce QEMU/systemd tight loop.
Prior to using this configuration you have to install edi according to this instructions.
Once edi is installed and this configuration cloned, a container can be generated using the following command:
sudo edi -v lxc configure qemu-buster qemu-buster.ymlPlease note that systemd and journalctl within the container eat 100% CPU time each.
The affected container can be entered as follows
lxc exec qemu-buster bashWithin the container the following command shows the tight loop:
qemu-aarch64-static --strace /bin/systemctl statusIt looks like systemd is stuck here:
2837 getsockopt(3,1,31,274891889456,274887218756,274888927920) = -1 errno=34 (Numerical result out of range)
2837 getsockopt(3,1,31,274891889456,274887218756,274888927920) = -1 errno=34 (Numerical result out of range)
2837 getsockopt(3,1,31,274891889456,274887218756,274888927920) = -1 errno=34 (Numerical result out of range)
2837 getsockopt(3,1,31,274891889456,274887218756,274888927920) = -1 errno=34 (Numerical result out of range)The container can be stopped using the following command:
lxc stop -f qemu-buster