On 06/21/2018 11:59 AM, Vladimir Sementsov-Ogievskiy wrote: > 20.06.2018 23:58, John Snow wrote: >> Vladimir, can you jog our memories and let us know which series still >> need to hit QEMU for 3.0 for safe persistence/migration et al? >> >> (Not including any of my own qemu-img patches which I'll get to by >> freeze.) > > not a trivial question :) > > at least, there are the following pending patches: > > migration > [PATCH] migration: invalidate cache before source start >
I have to look. > persistance > [PATCH v2] qcow2: add overlap check for bitmap directory Needs an eye by Kevin or Max. > [PATCH] block/qcow2: fix logic around dirty_bitmaps_loaded You're planning to send a V2, yes? > thread "bug in reopen arch", there is no final solution for now I'll catch up. > also, I need to finally rethink and make a patch to don't have any > persistent bitmaps in inactive mode > Or at least reload then on re-activate... > fleecing > [PATCH] block/fleecing-filter: new filter driver for fleecing (new > patch, but I remember, I've already started to discuss this..) > On my plate to review. Otherwise, I think Eric has pulled most of the patches he intended to, had a spec-based fix for NBD (which you and I already reviewed) and has a hack that serves as a PoC for libvirt-based testing I intend to look over shortly. >From my end, I need to rethink my qemu-img patches to either avoid the bm_list cache issue or solve the problems you identified; and I'm waiting to see if Nikolay or Eric would find the n-ary bitmap merge useful. Thank you, --John