On 2022-01-12 10:58, Christian Kastner wrote: > On 2022-01-12 20:14, Christian Kastner wrote: > > Addendum: I'm now occasionally also seeing this with arm64 when using > > sbuild with --chroot-mode=autopkgtest. I'd say it's 50/50 between > > success and failure. > > Yet another data point: by reducing the CPU count to 1, it seems that > the success rate climbs to 100% on arm64.
I also encountered this with an arm64 qemu image, and the count of CPUs seems indeed to be the key difference between success and failure. On my system, the following works fine: $ autopkgtest -- qemu --cpus=1 --qemu-architecture=aarch64 /var/tmp/autopkgtest-unstable-arm64.img Any value of --cpus greater than 1 fails consistently as follows. $ autopkgtest -- qemu --cpus=2 --qemu-architecture=aarch64 /var/tmp/autopkgtest-unstable-arm64.img autopkgtest [16:53:30]: starting date: 2022-10-13 autopkgtest [16:53:30]: version 5.26 autopkgtest [16:53:30]: host ariel; command line: /usr/bin/autopkgtest -- qemu --cpus=2 --qemu-architecture=aarch64 /var/tmp/autopkgtest-unstable-arm64.img qemu-system-aarch64: -drive if=pflash,format=raw,unit=0,read-only,file=/usr/share/AAVMF/AAVMF_CODE.fd: warning: short-form boolean option 'read-only' deprecated Please use read-only=on instead qemu-system-aarch64: terminating on signal 15 from pid 86611 (/usr/bin/python3) <VirtSubproc>: failure: The VM does not start a root shell on ttyS1 or hvc1 already. The only other supported login mechanism is through --user and --password on the guest ttyS0 autopkgtest [16:54:04]: ERROR: testbed failure: unexpected eof from the testbed
