Since the bare metal case reports a memory issue on the crashes, let us give it a bit more memory - with 2G it works finally.
Instead of the other tests in launchpad/canonistack this uses KVM mode via "-machine accel=kvm -enable-kvm -cpu host". Switching that instead to "-machine accel=tcg" it fails the same.
But I found what consumed all the memory, the guest is (by default) started with the same CPU set as the host which means -smp 156. Disabling SMT in general on the host and starting the guest with 4 cpus allows to reduce the memory to 1G (but 512M still fails). Some other environment detail seems to bump the memory demand up.
As a cross check I can it on canonistack with 2G but it still fails with the segfaults.
With the adapted config it worked in qemu 5.2 in KVM and TCG mode.
Since the bare metal case reports a memory issue on the crashes, let us give it a bit more memory - with 2G it works finally.
Instead of the other tests in launchpad/ canonistack this uses KVM mode via "-machine accel=kvm -enable-kvm -cpu host". Switching that instead to "-machine accel=tcg" it fails the same.
But I found what consumed all the memory, the guest is (by default) started with the same CPU set as the host which means -smp 156. Disabling SMT in general on the host and starting the guest with 4 cpus allows to reduce the memory to 1G (but 512M still fails). Some other environment detail seems to bump the memory demand up.
As a cross check I can it on canonistack with 2G but it still fails with the segfaults.
With the adapted config it worked in qemu 5.2 in KVM and TCG mode.