Comment 11 for bug 1992653

We could also think about binfmt having a different behavior in container/bare-metal but it should behave the same in VM/bare-metal and that is not what I see.
Well actually I do not know yet, let me add a Jammy VM run ...

And on my normal system I didn't run in the home dir, so another testcase ...

Thomas
(1) - ?? - Jammy -> Kinetic ?? VM -> fails
(2) - ?? - Jammy -> fails
Björn
(3) - ?? - Kinetic Fails
Paride
(4) - ?? - Kinetic -> works
(5) - ?? - Jammy -> Kinetic LXD VM -> works
Christian:
(6) - Intel - Jammy -> Kinetic LXD container -> works
(7) - Intel - Jammy -> Jammy LXD container -> works
(8) - Intel - Jammy -> fails
(9) - Intel - Jammy -> Kinetic libvirt VM (cpu=passthrough) -> works
(10) - Intel - Jammy -> Kinetic libvirt VM (cpu=qemu64) -> works
(11) - Intel -> Jammy -> Jammy libvirt VM /tmp via sudo -> works
(12) - Intel -> Jammy -> Jammy libvirt VM /root as root -> works

Hmm, I had some hope but (8) vs (11) should really be the same - out of ideas for now.
The only difference is that (11) is new and clean and who knows what i've done to my laptop (8) in the past ... :-/