Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1684449 - Can clear a disabled bitmap
Summary: Can clear a disabled bitmap
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: John Snow
QA Contact: aihua liang
Depends On: 1684441
TreeView+ depends on / blocked
Reported: 2019-03-01 10:03 UTC by aihua liang
Modified: 2019-03-06 20:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1684441
Last Closed: 2019-03-06 20:26:20 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

Comment 1 aihua liang 2019-03-01 10:03:57 UTC
Test on qemu-kvm-3.1.0-18.module+el8+2834+fa8bb6e2.x86_64, also hit this issue.

Comment 2 John Snow 2019-03-06 20:26:20 UTC
Hi, upstream we decided explicitly to allow this behavior for reasons that are kind of obtuse, however:

The idea is that "enabled" and "disabled" mean more "the bitmap is recording writes from the guest" or "the bitmap is not recording writes from the guest" and we no longer prohibit the user from manually clearing bitmaps.

Example usage:

- Create a new bitmap
- Disable that bitmap
- Use that bitmap as a merge target for other bitmaps. It has been disabled so that it does not pick up new writes by accident.

Because we have a valid use case for modifying a disabled bitmap, a decision was made to allow all such user initiated modifications, including clear/reset and merge.

I'm sorry for not having communicated this sooner.

Note You need to log in before you can comment on or make changes to this bug.