Bug 1956429 - NVMe devices missing bootindex property in v5.2
Summary: NVMe devices missing bootindex property in v5.2
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-03 16:44 UTC by Jonathan Lebon
Modified: 2021-05-03 20:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Jonathan Lebon 2021-05-03 16:44:44 UTC
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.

Comment 1 Philippe Mathieu-Daudé 2021-05-03 17:43:12 UTC
Yes, commit 498114b37bc ("hw/block/nvme: expose 'bootindex' property") is enough.


Note You need to log in before you can comment on or make changes to this bug.