Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
As ivshmem has been replaced by ivshmem-plain and ivshmem-doorbell. And qemu doesn't support 'ivshmem', but still can query it. So the querying should be disabled in qemu, because it may confuse people.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.6.0-23.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. qemu fails start with ivshmem
# /usr/libexec/qemu-kvm -m 4G -device ivshmem,size=4G,shm=shmem0
qemu-kvm: -device ivshmem,size=4G,shm=shmem0: Parameter 'driver' expects pluggable device type
qemu-kvm-rhev-2.3.0-31.el7_2.3.x86_64 support
qemu-kvm-rhev-2.6.0-23.el7.x86_64 not support as above show
2. But qemu still shows it's supported. So this querying should be disabled.
# /usr/libexec/qemu-kvm -device ivshmem,?
ivshmem.ioeventfd=bool (on/off)
ivshmem.rombar=uint32
ivshmem.x-pcie-lnksta-dllla=bool (on/off)
ivshmem.use64=uint32
ivshmem.shm=str
ivshmem.multifunction=bool (on/off)
ivshmem.msi=bool (on/off)
ivshmem.size=str
ivshmem.romfile=str
ivshmem.command_serr_enable=bool (on/off)
ivshmem.vectors=uint32
ivshmem.addr=int32 (Slot and optional function number, example: 06.0 or 06)
ivshmem.chardev=str (ID of a chardev to use as a backend)
ivshmem.role=str
Actual results:
qemu can still query it.
Expected results:
As it's actually not supported, so the querying of ivshmem should be disabled.
Additional info:
(In reply to Pei Zhang from comment #1)
> Seems even some devices becomes not supported, it's still not disabled in
> qemu. So close this bug.
>
It's not reasonable, please ignore it.
My understanding is that this is not a problem as we don't support direct invocation of QEMU. Anyway, reassigning to Markus for validation.
Comment 5Markus Armbruster
2016-09-09 14:44:13 UTC
We use various ways to disable unwanted device models. One of them
marks them "no-user". These cannot be used with -device. "-device
help" and "device_add help" don't show them. However, "info qdm"
still shows them, and "-device DEV-MODEL,help" / "device_add
DEV-MODEL,help" still works. This is normal.