diff options
| author | Denys Fedoryshchenko <denys.f@collabora.com> | 2026-06-10 15:57:46 +0300 |
|---|---|---|
| committer | Denys Fedoryshchenko <denys.f@collabora.com> | 2026-06-10 15:57:46 +0300 |
| commit | 0484b5d7c6c11f6ae832bf504d528e04d5fa31aa (patch) | |
| tree | 53840efeddf4180a125bb45f16f253a363f852d7 /kernel/driver | |
| parent | f2aec6230773177c9449542f92730ca3de0d307e (diff) | |
| download | accel-ppp-0484b5d7c6c11f6ae832bf504d528e04d5fa31aa.tar.gz accel-ppp-0484b5d7c6c11f6ae832bf504d528e04d5fa31aa.zip | |
ci: harden s390x qemu test against modloop/disk flakes
The s390x netboot initramfs ships virtio_net but not virtio_blk; the
block driver only becomes available after the modloop image is
downloaded over the network at boot. When that download fails, sshd
still comes up but /dev/vda never appears and setup-disk dies with
"/dev/vda is not a block device suitable for partitioning".
- Wait for /sys/block/vda/device before running setup-alpine,
restarting the modloop and hwdrivers services on each retry.
- Log the QEMU console (screen -L) for both VM launches and dump the
logs at the end of the job, so failures of the second boot (the
other recurring flake, where ssh never comes back after reboot)
are debuggable.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Diffstat (limited to 'kernel/driver')
0 files changed, 0 insertions, 0 deletions
