[pve-devel] copy_vm: new option -target

Stefan Priebe - Profihost AG s.priebe at profihost.ag
Thu May 2 13:21:08 CEST 2013

Am 02.05.2013 13:09, schrieb Alexandre DERUMIER:
>>> Should be possible to fix qemu-img? 
> Yes, I think it should be possible. Code is not so huge.
> But Maybe do you have a better understanding of the code. (As you have played with backup ;)
> What I don't understand if the format change from v2 to v1.
> qemu-img convert should only copy block sector from source to target, and I think that rbd format infos are outside the volume.

Yes they're outside of the volume. So i think qemu-img does not have
access to them. The only i idea i have is:
1.) disk must be created before
2.) qemu-img must skip blocks with 0 for rbd


> ----- Mail original ----- 
> De: "Dietmar Maurer" <dietmar at proxmox.com> 
> À: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag>, "Alexandre DERUMIER" <aderumier at odiso.com> 
> Cc: pve-devel at pve.proxmox.com 
> Envoyé: Jeudi 2 Mai 2013 13:03:13 
> Objet: RE: [pve-devel] copy_vm: new option -target 
>> I also read that we'll loose sparseness with qemu-img as it does raw export and 
>> import. 
>> The best way would be to use rbd cp in this case which does all the things. 
> Should be possible to fix qemu-img? 

More information about the pve-devel mailing list