[pve-devel] copy_vm: new option -target

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


Hi Alexandre,

have you checked which rbd format qemu-img creates? I mean we have rbd
format 1 and format 2.

In my tests qemu-img always create the slower and older format v1. But
normally if we clone a VM we should have the same settings of source and
target disk.

Greets,
Stefan

Am 02.05.2013 11:17, schrieb Alexandre DERUMIER:
>>> Ah, OK. I thought we already check that for migrate? 
>  Yes, indeed
> 
>            # check if storage is available on both nodes
>             my $scfg = PVE::Storage::storage_check_node($self->{storecfg}, $sid);
>             PVE::Storage::storage_check_node($self->{storecfg}, $sid, $self->{node});
> 
> But not in pve-manager. (I think we display all nodes).
> 
> 
> But for vm_copy maybe we can readd this check 
> 
> 
> 
> ----- Mail original ----- 
> 
> De: "Dietmar Maurer" <dietmar at proxmox.com> 
> À: "Alexandre DERUMIER" <aderumier at odiso.com> 
> Cc: pve-devel at pve.proxmox.com 
> Envoyé: Jeudi 2 Mai 2013 09:03:46 
> Objet: RE: copy_vm: new option -target 
> 
>>>> I thought we assume a shared storage is always available (unless disabled)? 
>> It's possible that a shared can be assigned to specific nodes only. (nodes xxxx in 
>> storage.cfg). 
>> I have some shared storage in production not shared on all servers in same 
>> cluster. (because of differents networks) 
> 
> Ah, OK. I thought we already check that for migrate? 
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 



More information about the pve-devel mailing list