On 09/03/2026 17.49, Thomas Huth wrote:
On 09/03/2026 01.36, [email protected] wrote:
From: Jared Rossi <[email protected]>
Add a rudimentary test for s390x IPL to verify that a guest may boot using
virtio-blk-pci device.
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Jared Rossi <[email protected]>
---
tests/qtest/cdrom-test.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tests/qtest/cdrom-test.c b/tests/qtest/cdrom-test.c
index 56e2d283a9..a65854d2bc 100644
--- a/tests/qtest/cdrom-test.c
+++ b/tests/qtest/cdrom-test.c
@@ -246,6 +246,13 @@ static void add_s390x_tests(void)
"-drive if=none,id=d2,media=cdrom,file=",
test_cdboot);
}
+ if (qtest_has_device("virtio-blk-pci")) {
+ qtest_add_data_func("cdrom/boot/pci-bus-with-bootindex",
+ "-device virtio-scsi -device virtio-serial "
+ "-device virtio-blk-pci,drive=d1,bootindex=1 "
+ "-drive if=none,id=d1,media=cdrom,file=",
+ test_cdboot);
+ }
}
Hi Jared!
While testing your series, it seems like the cdrom-test is now triggering a
segmentation fault in QEMU here ... not sure whether I did something wrong
on my side while building the bios, or whether there is a bug somewhere?
Does this qtest work for you with this v5 series?
Ah, it's working on my s390x LPAR, but it's failing on my x86 laptop ...
maybe there is some endianness issue left somewhere?
Thomas
