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.
Bug 1392328 - Disable new devices in QEMU 2.8 (x86_64)
Summary: Disable new devices in QEMU 2.8 (x86_64)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Miroslav Rezanina
QA Contact: Chao Yang
URL:
Whiteboard:
Depends On: 1393698
Blocks: 1387600 1422349
TreeView+ depends on / blocked
 
Reported: 2016-11-07 08:36 UTC by Miroslav Rezanina
Modified: 2020-09-24 08:40 UTC (History)
14 users (show)

Fixed In Version: qemu-kvm-rhev-2.8.0-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 23:39:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2392 0 normal SHIPPED_LIVE Important: qemu-kvm-rhev security, bug fix, and enhancement update 2017-08-01 20:04:36 UTC

Description Miroslav Rezanina 2016-11-07 08:36:23 UTC 
Disable new devices introduced with rebase to QEMU 2.7:

- qemu,register
- vfio-pci-igd-lpc-bridge
Comment 1 Miroslav Rezanina 2017-01-23 09:22:25 UTC 
We rebased to 2.8 instead of 2.7 so we need to remove devices added in 2.8 too.

List of new devices:

- floppy
- vhost-vsock-device
- vhost-vsock-pci
- virtio-crypto-device
- virtio-crypto-pci
- amd-iommu
- AMDVI-PCI
- loader
- or-irq

vhost-vsock-device (and vhost-vsock-pci) are requested by bz #1291284.

floppy device is qomified  floppy device, we want to keep the functionality without allowing command-line access.
Comment 2 Miroslav Rezanina 2017-02-20 10:06:36 UTC 
Fix included in qemu-kvm-rhev-2.8.0-5.el7
Comment 4 Chao Yang 2017-06-01 09:35:49 UTC 
Steps to verify this bug:

1. re-compile source code and compare build log on unfixed and fixed version

or-irq.o, generic-loader.o, amd_iommu.o, virtio-crypto-pci.o, register.o was observed on qemu-kvm-rhev-2.8.0-3.el7.x86_64 but on qemu-kvm-rhev-2.9.0-7.el7 otherwise.



2. check output of -device ? 

on qemu-kvm-rhev-2.8.0-3.el7.x86_64 

Storage devices:
name "floppy", bus floppy-bus, desc "virtual floppy drive"

Network devices:
name "virtio-crypto-device", bus virtio-bus
name "virtio-crypto-pci", bus PCI

Uncategorized devices:
name "amd-iommu", bus System
name "AMDVI-PCI", bus PCI
name "loader", desc "Generic Loader"
name "or-irq"
name "qemu,register"
name "vfio-pci-igd-lpc-bridge", bus PCI, desc "VFIO dummy ISA/LPC bridge for IGD assignment"


on qemu-kvm-rhev-2.9.0-7.el7, neither of above was observed. 





Setting VERIFIED.
Comment 6 errata-xmlrpc 2017-08-01 23:39:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 7 errata-xmlrpc 2017-08-02 01:17:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 8 errata-xmlrpc 2017-08-02 02:09:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 9 errata-xmlrpc 2017-08-02 02:50:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 10 errata-xmlrpc 2017-08-02 03:14:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 11 errata-xmlrpc 2017-08-02 03:35:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Note You need to log in before you can comment on or make changes to this bug.