Description of problem: Sometimes during the f40 release cycle, the s390x Cloud images ceased to boot in VMs. I initially found out through testcloud, but the same issue happens on plain libvirt and plain qemu on Mac OS X host. Version-Release number of selected component (if applicable): kiwi that was used to build Fedora 40 GA libvirt-10.1.0-1.fc40.x86_64 qemu-system-s390x-core-8.2.2-1.fc40.x86_64 How reproducible: Always Steps to Reproduce: 1. testcloud create fedora:40 --arch s390x --timeout 3600 2. Or click through virt-manager wizard, add a new s390x vm, add Cloud GA image Actual results: Console spammed with on f40: [88.446604] dracut-initqueue[461]: Warning: dracut-initqueue: starting timeout scripts [ 389.642568] dracut-initqueue[461]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 389.674278] dracut-initqueue[461]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fe2d29979-23d3-432e-a363-ab1c099d27e5.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then [ 389.675665] dracut-initqueue[461]: [ -e "/dev/disk/by-uuid/e2d29979-23d3-432e-a363-ab1c099d27e5" ] [ 389.676857] dracut-initqueue[461]: fi" Rawhide fails earlier with: ! BPRS read failed! LOADPARM=[ ] Using virtio-blk. Using guessed DASD geometry. Using ECKD scheme (block size 4096), List-Directed Expected results: System booted up. Additional info: Similar but different regression occurred on ppc64le where it fails at an earlier stage: https://bugzilla.redhat.com/show_bug.cgi?id=2283979 . Rawhide is affected too, f39 works fine. Also, I am not sure that kiwi is the culprit, but we have to start somewhere.
Created attachment 2035707 [details] libvirt xml template
This is going to be fixed in kiwi 1.0.21 and with the recent update to the descriptions.
FEDORA-EPEL-2024-94eb09382f (kiwi-10.0.21-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-94eb09382f
FEDORA-2024-0cd63505c9 (kiwi-10.0.21-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0cd63505c9
FEDORA-2024-8ecf843eb0 (kiwi-10.0.21-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-8ecf843eb0
FEDORA-2024-8ecf843eb0 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-8ecf843eb0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8ecf843eb0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-94eb09382f has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-94eb09382f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-0cd63505c9 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-0cd63505c9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0cd63505c9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-0cd63505c9 (kiwi-10.0.21-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-94eb09382f (kiwi-10.0.21-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-8ecf843eb0 (kiwi-10.0.21-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.