On 2018-04-16 16:59, Alberto Garcia wrote: > On Fri 13 Apr 2018 04:23:07 PM CEST, Max Reitz wrote: >> On 2018-04-12 19:07, Alberto Garcia wrote: >>> Hello, >>> >>> I mentioned this some time ago, but I'd like to retake it now: I'm >>> checking how to copy arbitrary nodes on a backing chain, so if I have >>> e.g. >>> >>> [A] <- [B] <- [C] <- [D] >>> >>> I'd like to end up with >>> >>> [A] <- [E] <- [C] <- [D] >>> >>> where [E] is a copy of [B]. The most obvious use case is to move [B] >>> to a different storage backend. >>> >>> At the moment we can already copy [B] into [E] (outside QEMU) and then >>> do >>> >>> change-backing-file device=[D] image-node-name=[C] backing-file=[E] >>> >>> However this only changes the image on disk and the bs->backing_file >>> string in memory. QEMU keeps using the [B] BlockDriverState, and we >>> need to make it switch to [E]. >>> >>> One possible way to do this would be to modify blockdev-mirror so the >>> source image can be located anywhere on a chain. Currently there's >>> bs->backing_blocker preventing that, plus qmp_blockdev_mirror() >>> refuses to take any non-root source node. Other than permission >>> changes I don't think the algorithm itself needs any additional >>> modification, although I suppose we'd like to change the backing file >>> as part of the same job, and that would require API changes. >> >> Another way would be to write blockdev-copy. :-) > > Something like blockdev-backup but without copying data from backing > files? blockdev-mirror already allows configuring that using the > MirrorSyncMode parameter.
No, a block job that unites blockdev-backup, blockdev-mirror, and block-commit. Active commit already is just mirror, non-active commit probably can easily be implemented with mirror (we just need an auto-complete), and it should be possible to add a backup mode to mirror (like active mirroring). So we'd just have a single blockdev-copy job that can simply... Copy data from any node to any other. I think we wanted to exclude streaming, because that works differently. But, well, streaming would be just installing a COR filter node and doing a blockdev-copy to null-co://, right? :-) >> I don't think there should be a limitation which nodes can be used as >> the source of blockdev-mirror, and I think the hardest part about >> lifting that limitation is about thinking what might break... Maybe >> we should just drop the limitation and deal with the fallout later? I >> can't imagine a single node configuration where we'd want to disallow >> copying off a node, so I suppose if that breaks in some edge case that >> wouldn't be something we'd have to disallow again but we'd just have >> to fix it. > > I can't think of any problem either. The important question is what to > do if the source node is read/write, but that's what blockdev-mirror is > already about. In all other cases the source node is going to be read > only, isn't it? I guess so. I just now remembered a bitmap issue, but that probably shouldn't stop you. There is an issue with bitmaps on nodes with shared-writing children. Imagine you have some qcow2 node or whatever, and you have a guest running on it. Then you attach a filter to it (which allows shared writing) and put a mirror job on top of the filter. Now whenever the guest writes to the qcow2 node, the bitmap the mirror job installed on the filter won't reflect that. So that's an issue, but I think that case isn't forbidden by the current permission system, so we're already screwed there. So on the contrary, I'd suspect that running mirror inside of some backing chain or whatever may be less problematic than running it on top, actually... >>> One other way is to have a more generic replace-node command which >>> would call bdrv_replace_node(), but I don't know if we want to expose >>> that and I don't have any other use case for it at the moment. >> >> I think we do want to expose that. As far as I'm informed, for graph >> manipulation we want a command that can replace nodes (including >> replacing nothing by a new node or replacing an existing node by >> nothing, if the parent supports that). > > Was there any discussion about this in the mailing list? (proposed name > for this function, features, etc.) Well, there is x-blockdev-change. But we probably want to expose bdrv_reopen() in the long run. http://lists.nongnu.org/archive/html/qemu-block/2017-12/msg00522.html is what I can offer you. That also has some info on blockdev-copy and the bitmap issue ("omniscient bitmaps" is the keyword). Max >> Also, well, there is blockdev-mirror already has a @replaces >> parameter, right? That was supposed to work with quorum, but it seems >> obvious to use it here, too. > > Yes, it could be used for this. > > Berto >
Description: OpenPGP digital signature