On Thu, 2023-06-01 at 18:58 +0200, Pierre-Elliott Bécue wrote: > > I should have time this weekend when I can spin up a qemu vm to > > test in, if we're not able to get a root cause identified before > > then.
I did try to reproduce the issue over the weekend with qemu. Using qemu-user-static and systemd-nspawn was insufficient due to lxcfs needing proper access to the fuse kernel api. After trying and failing to bootstrap an armhf instance by hand, I grabbed a raspberry pi 2 bookworm image from raspi.d.n, and got it running under qemu-system- arm. Within that environment, lxcfs appeared to work correctly (/var/lib/lxcfs/proc/cpuinfo was correct, no obvious errors or warnings noticed). I didn't spin up a full lxc container instance within that environment. > I can probably grant you privileges on abel as soon as I get an ack > from my fellow DSA mates. If it's possible to get temporary permissions on abel, that would be useful. One other thing to double check on ci-worker-armhf-01 would be the contents of /var/lib/lxcfs/proc/cpuinfo, so we can see what lxcfs is doing from the host side. Mathias
signature.asc
Description: This is a digitally signed message part
