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 1472271 - Rebase virt-manager to current upstream release
Summary: Rebase virt-manager to current upstream release
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
Jiri Herrmann
URL:
Whiteboard:
Depends On:
Blocks: 1469590 1562102
TreeView+ depends on / blocked
 
Reported: 2017-07-18 10:36 UTC by Jaroslav Suchanek
Modified: 2018-04-10 11:42 UTC (History)
5 users (show)

Fixed In Version: virt-manager-1.4.3-1.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
_virt-manager_ rebased to 1.4.3 The _virt-manager_ packages have been upgraded to version 1.4.3, which provides a number of bug fixes and enhancements over the previous version. Notable changes include: * The virt-manager interface now displays the correct CPU models when creating a guest virtual machine that does not use the AMD64 and Intel 64 architectures. * The default device selection has been optimized for guests using the IBM POWER, IBM z Systems, or the 64-bit ARM architectures. * If an installed network card on the host system is compatible with single root I/O virtualization (SR-IOV), it is now possible to create a virtual network that lists a pool of available virtual functions of the selected SR-IOV-capable card. * The selection of OS types and versions for a newly created guest has been expanded.
Clone Of:
: 1562102 (view as bug list)
Environment:
Last Closed: 2018-04-10 11:40:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0726 0 None None None 2018-04-10 11:42:12 UTC

Description Jaroslav Suchanek 2017-07-18 10:36:03 UTC 
Rebase virt-manager to latest upstream release to include new features and resolve rhel bugs, that are already fixed/will be fixed in upstream.
Comment 2 Jaroslav Suchanek 2017-12-11 13:15:23 UTC 
Please provide text for release notes. Thanks.
Comment 3 zhoujunqin 2018-02-09 08:45:43 UTC 
We have done functional testing and acceptance testing for package "virt-manager-1.4.3-3.el7.noarch", since no critical regression bugs were found, I move this bug from ON_QA to VERIFIED, thanks.
Comment 6 errata-xmlrpc 2018-04-10 11:40:46 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/RHEA-2018:0726
Note You need to log in before you can comment on or make changes to this bug.