Bug 1677073
Summary: | Backport additional QEMU 4.0 Bitmap API changes to RHEL 7.7 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | John Snow <jsnow> |
Component: | qemu-kvm-rhev | Assignee: | John Snow <jsnow> |
Status: | CLOSED ERRATA | QA Contact: | aihua liang <aliang> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.7 | CC: | areis, chayang, coli, juzhang, ngu, virt-maint |
Target Milestone: | rc | Keywords: | FeatureBackport |
Target Release: | 7.7 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.12.0-27.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-22 09:20:23 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: |
Description
John Snow
2019-02-13 23:14:42 UTC
Fix included in qemu-kvm-rhev-2.12.0-27.el7 Verified on qemu-kvm-rhev-2.12.0-27.el7.x86_64, except issue in comment 7 and in bug 1703916, others works ok. After comment7 confirmed, will set the bug's status to "Verified" and track the left issue by the new reported bugs. Ah... I realize that I went out of my way to document that the anonymous bitmaps would not be user-visible, but it's actually not true. They *can* be visible... It's just that you cannot address them with any of the bitmap commands because they do not have a name. It is probably too late to hide this from the user (as this has been the case for some time), so I will change the documentation to say that anonymous bitmaps MIGHT be visible. I would say that this is unintentional, but not a bug, and not harmful except that it may serve to confuse. Thank you, --John According to comment8 & comment9, set bug's status to "verified". And John will update the doc later. 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-2019:2553 |