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 817565 - 'qemu' package should be 'qemu-kvm'
Summary: 'qemu' package should be 'qemu-kvm'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Miroslav Rezanina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-30 14:06 UTC by Eduardo Habkost
Modified: 2014-06-18 03:15 UTC (History)
7 users (show)

Fixed In Version: qemu-kvm-1.3.0-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 13:11:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Eduardo Habkost 2012-04-30 14:06:58 UTC 
On RHEL7 the qemu package will be KVM-specific, and other qemu flavors/targets won't be built.

To make this clear and avoid potential conflicts with third-party full-feature non-KVM-specific qemu packages, the package should be renamed to qemu-kvm.
Comment 1 Bill Nottingham 2012-04-30 17:47:50 UTC 
The binary or source package?
Comment 2 Eduardo Habkost 2012-04-30 18:08:47 UTC 
I was planning to change both, but I am not sure.

On the one hand, we don't need to care about the source package name, as conflicts only matter for the binary RPMs (so the src.rpm could still be named 'qemu'). On the other hand, by changing the src RPM name to match the resulting binary RPM names, it will probably result in less change in the spec file, simpler code, and less divergence from the Fedora spec.
Comment 6 Richard W.M. Jones 2012-05-14 18:29:43 UTC 
I really like TCG, and more to the point we need it for virt-v2v.

Also I don't understand why we need to rename the package.
We should keep things as close as possible to Fedora to
avoid RHEL-specific patches, except where it's necessary.
Comment 7 Daniel Berrangé 2012-05-15 08:59:37 UTC 
Agreed that we should keep TCG enabled in the qemu-kvm binary. It is very important to be able to run the full libguestfs testsuite during builds to avoid regressions during updates.

The rationale for calling it qemu-kvm is to allow EPEL to provide a plain 'qemu' RPM containing all the non-KVM based emulators without conflicting. This is the same as we did for RHEL-6
Comment 8 juzhang 2013-10-28 04:12:43 UTC 
Verified with qemu-kvm-1.5.3-10.el7, all packages are qemu-kvm related.
Comment 9 Ludek Smid 2014-06-13 13:11:44 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.