Bug 1343891

Summary:	Disable spapr-rng device in downstream qemu 2.6
Product:	Red Hat Enterprise Linux 7	Reporter:	Thomas Huth <thuth>
Component:	qemu-kvm-rhev	Assignee:	Miroslav Rezanina <mrezanin>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	jen, knoel, lvivier, michen, qzhang, virt-maint, xuhan, zhengtli
Target Milestone:	rc
Target Release:	---
Hardware:	ppc64le
OS:	Linux
Whiteboard:
Fixed In Version:	qemu-kvm-rhev-2.6.0-6.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-07 21:15:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1289417
Bug Blocks:	1333282

Description Thomas Huth 2016-06-08 09:02:51 UTC

In BZ 1337557 we came to the conclusion that we won't support the spapr-rng device in qemu-kvm-rhev. Since the device is currently available by default due to the rebase to QEMU 2.6.0, we should now make sure that it gets disabled in the downstream version again.

Comment 1 Miroslav Rezanina 2016-06-15 13:08:52 UTC

Fix included in qemu-kvm-rhev-2.6.0-6.el7

Comment 3 mazhang 2016-06-21 02:34:29 UTC

Test this bug on qemu-kvm-rhev-2.6.0-7.el7.ppc64le.

# /usr/libexec/qemu-kvm -device ? 2>&1 |grep rng
name "virtio-rng-device", bus virtio-bus
name "virtio-rng-pci", bus PCI, alias "virtio-rng"
# /usr/libexec/qemu-kvm -device spapr-rng,id=rng0
qemu-kvm: -device spapr-rng,id=rng0: 'spapr-rng' is not a valid device model name

spapr-rng device has been disabled.

Comment 5 errata-xmlrpc 2016-11-07 21:15:53 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://rhn.redhat.com/errata/RHBA-2016-2673.html