[PATCH 1/2] qcow2: Release read-only bitmaps when inactivated

2020-07-30 Thread Max Reitz
During migration, we release all bitmaps after storing them on disk, as long as they are (1) stored on disk, (2) not read-only, and (3) consistent. (2) seems arbitrary, though. The reason we do not release them is because we do not write them, as there is no need to; and then we just forget about

Re: [PATCH 1/2] qcow2: Release read-only bitmaps when inactivated

2020-07-30 Thread Peter Krempa
On Thu, Jul 30, 2020 at 14:02:33 +0200, Max Reitz wrote: > During migration, we release all bitmaps after storing them on disk, as > long as they are (1) stored on disk, (2) not read-only, and (3) > consistent. > > (2) seems arbitrary, though. The reason we do not release them is > because we do

Re: [PATCH 1/2] qcow2: Release read-only bitmaps when inactivated

2020-07-30 Thread Eric Blake
On 7/30/20 7:02 AM, Max Reitz wrote: During migration, we release all bitmaps after storing them on disk, as long as they are (1) stored on disk, (2) not read-only, and (3) consistent. (2) seems arbitrary, though. The reason we do not release them is because we do not write them, as there is no

Re: [PATCH 1/2] qcow2: Release read-only bitmaps when inactivated

2020-08-05 Thread Vladimir Sementsov-Ogievskiy
30.07.2020 15:02, Max Reitz wrote: During migration, we release all bitmaps after storing them on disk, as long as they are (1) stored on disk, (2) not read-only, and (3) consistent. (2) seems arbitrary, though. The reason we do not release them is because we do not write them, as there is no n