arm64be tuxrun test is sometimes failing with I/O errors

The arm64be tuxrun test is sometimes failing with I/O errors.

First seen here where I tried to convert the test to the new functional framework:

https://lore.kernel.org/qemu-devel/9a267d01-1259-4e2a-8ad6-e963923bed2c@redhat.com/

The convertion has never been merged yet, but now we also hit this problem with the old Avocado-based version of the test:

https://gitlab.com/qemu-project/qemu/-/jobs/8398322343

Quoting from the debug log of that test run:

[stdlog] 2024-11-18 10:51:30,096 console __init__         L0151 DEBUG| Starting syslogd: OK
[stdlog] 2024-11-18 10:51:30,172 console __init__         L0151 DEBUG| Starting klogd: OK
[stdlog] 2024-11-18 10:51:30,428 console __init__         L0151 DEBUG| Running sysctl: OK
[stdlog] 2024-11-18 10:51:30,521 console __init__         L0151 DEBUG| Saving 2048 bits of non-creditable seed for next boot
[stdlog] 2024-11-18 10:51:30,911 console __init__         L0151 DEBUG| Starting network: OK
[stdlog] 2024-11-18 10:51:31,068 console __init__         L0151 DEBUG| Welcome to TuxTest
[stdlog] 2024-11-18 10:51:31,769 console __init__         L0151 DEBUG| tuxtest login: blk_update_request: I/O error, dev vda, sector 5824 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[stdlog] 2024-11-18 10:51:31,769 console __init__         L0151 DEBUG| blk_update_request: I/O error, dev vda, sector 8848 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[stdlog] 2024-11-18 10:51:31,769 console __init__         L0151 DEBUG| blk_update_request: I/O error, dev vda, sector 12936 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[stdlog] 2024-11-18 10:51:31,775 console __init__         L0151 DEBUG| root
[stdlog] 2024-11-18 10:51:31,790 console __init__         L0151 DEBUG| blk_update_request: I/O error, dev vda, sector 17032 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[stdlog] 2024-11-18 10:51:31,798 console __init__         L0151 DEBUG| blk_update_request: I/O error, dev vda, sector 21128 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[stdlog] 2024-11-18 10:51:31,806 console __init__         L0151 DEBUG| blk_update_request: I/O error, dev vda, sector 25224 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[stdlog] 2024-11-18 10:51:31,814 console __init__         L0151 DEBUG| blk_update_request: I/O error, dev vda, sector 29320 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[stdlog] 2024-11-18 10:52:59,956 avocado.test stacktrace       L0040 ERROR| 

(looking at some older test logs, I can also see the I/O errors in there, they just occurred at different points in time so that the test did not fail, see e.g. https://gitlab.com/qemu-project/qemu/-/jobs/8391726583/artifacts/external_file/build/tests/results/latest/test-results/51-tests_avocado_tuxrun_baselines.py_TuxRunBaselineTest.test_arm64be/debug.log )