The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.18
-->
commit 7c032ad121651367118225b85601cacd060988f6
Author: Konstantin Khorenko
Date: Mon Feb 24 22:26:33 2025 +0300
Revert "c
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.18
-->
commit 37260588c8a3594b702c7b6f98983a93e3c962ad
Author: Konstantin Khorenko
Date: Mon Feb 24 22:29:50 2025 +0300
Revert "c
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.18
-->
commit 5990ec1f02a620b68af2541bb8164dff23016c53
Author: Andrey Zhadchenko
Date: Thu Feb 20 15:51:11 2025 +0300
dm-qcow2: p
On 20.02.25 14:51, Andrey Zhadchenko wrote:
Programs, which work with qcow2 files as writables, are
expected to reset autoclear_features bits which are unknown
to them. If qcow2 file has only inactive bitmaps, we may not
reset QCOW2_AUTOCLEAR_BITMAPS bit. Bitmaps are already allocated
and we are