Description of problem: Migrating coreos-assembler from f33 to f34, we're hitting: > qemu-system-x86_64: -device nvme,drive=d1,serial=primary-disk,bootindex=1: Property 'nvme.bootindex' not found And indeed in f34 (v5.2): $ qemu-kvm -device nvme,help | grep bootindex $ Whereas in f33 (v5.1): $ qemu-kvm -device nvme,help | grep bootindex bootindex=<int32> It looks fixed in rawhide (v6.0): $ qemu-kvm -device nvme,help | grep bootindex bootindex=<int32> Version-Release number of selected component (if applicable): $ rpm -q qemu-kvm qemu-kvm-5.2.0-5.fc34.1.x86_64 How reproducible: Always Steps to Reproduce: 1. Try to use `bootindex` property on NVMe devices Actual results: > qemu-system-x86_64: -device nvme,drive=d1,serial=primary-disk,bootindex=1: Property 'nvme.bootindex' not found Expected results: Works Additional info: Looks like the post-v5.2 fix for this upstream was in https://git.qemu.org/?p=qemu.git;a=commit;h=498114b37bc99fddcfc24b92bff7f1323fb32672 so hopefully it's just a straightforward backport.
Yes, commit 498114b37bc ("hw/block/nvme: expose 'bootindex' property") is enough.
FEDORA-2021-303ad002d2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-303ad002d2
FEDORA-2021-303ad002d2 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-303ad002d2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-303ad002d2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-303ad002d2 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.