QA (public) » openQA Project (public) » openQA Tests (public)

My findings:

1. I tried several different workers, none of them can work now
2. There is no changes for iso image, but need to double confirm if any kernel parameters changed or code change recently
3. I noticed that there were some packages update from worker side as well, I am not sure if the issue has something to do with the new OVMF/QEMU packages

Will investigate it.

The issue can still be seen with UEFI_PFLASH_CODE=/usr/share/qemu/ovmf-x86_64-code.bin UEFI_PFLASH_VARS=/usr/share/qemu/ovmf-x86_64-vars.bin

Is it possible to restore the previous snapshot of the worker to run the test again?

The issue can be reproduced with the ovmf binary files used in openQA worker as well. see https://suse.slack.com/archives/C02CANHLANP/p1726216772558129

Package details:

> rpm -qi qemu-ovmf-x86_64-202405-Virt.150500.300.1.noarch
Name        : qemu-ovmf-x86_64
Version     : 202405
Release     : Virt.150500.300.1
Architecture: noarch
Install Date: Thu 12 Sep 2024 05:24:26 AM UTC
Group       : System/Emulators/PC
Size        : 86721417
License     : BSD-2-Clause-Patent
Signature   : RSA/SHA256, Wed 11 Sep 2024 10:16:44 AM UTC, Key ID 9c753149ce3b672e
Source RPM  : ovmf-202405-Virt.150500.300.1.src.rpm
Build Date  : Wed 11 Sep 2024 10:15:10 AM UTC
Build Host  : h04-ch1a
Relocations : (not relocatable)
Vendor      : obs://build.suse.de/home:favogt:stagingovmf
URL         : https://github.com/tianocore/edk2
Summary     : Open Virtual Machine Firmware - QEMU rom images (x86_64)
Description :
The Open Virtual Machine Firmware (OVMF) project aims to support
firmware for Virtual Machines using the edk2 code base.

This package contains UEFI rom images for exercising UEFI secure
boot in a qemu environment (x86_64)
Distribution: home:favogt:stagingovmf / 15.5

https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/repos.sls#L48-61

On my workstation I had qemu-ovmf-x86_64-202402 installed and it booted fine. After installing the latest build (qemu-ovmf-x86_64-202405-Virt.1699.300.1.noarch) it failed.
This only happens if there is a virtio-rng-pci device attached.

FWICT this is fixed in OVMF with https://github.com/tianocore/edk2/pull/5690.

I filed https://bugzilla.suse.com/show_bug.cgi?id=1230587.

The SLEM test runs are also affected by this:

• https://openqa.suse.de/tests/15447004 (SLEM 5.5)
• https://openqa.suse.de/tests/15446784 (SLEM 5.4)
• https://openqa.suse.de/tests/15454921 (SLEM 5.3)
• https://openqa.suse.de/tests/15455022 (SLEM 5.2)
• https://openqa.suse.de/tests/15455021 (SLEM 5.1)

Suggested workaround: QEMU_VIRTIO_RNG=0

ph03nix wrote in #note-13:

Suggested workaround: QEMU_VIRTIO_RNG=0

Thanks @ph03nix

Added QEMU_VIRTIO_RNG=0 for machine uefi and uefi-no-secboot as a workaround for now. will remove it once the fix is ready