[pve-devel] storage migration: extend "qm migrate"?

Michael Rasmussen mir at datanom.net
Thu Jan 17 10:42:15 CET 2013


Hi,

I still can figure out why it should be necessary to migrate the vm if 
the storage is migrated to another host?

Especially in the situation where a host has more than one disk and you 
then migrate one of the disks. Should the vm still be migrated then? 
what about the remaining disks, should they be migrate as well?

In my opinion the user should decide whether to migrate the vm together 
with the storage or maintain the vm at the host where it is currently 
running.

On 01-17-2013 09:04, Alexandre DERUMIER wrote:
> Hi,
>
> I'm begin to look for storage migration implementation,
>
> do you think we need to extend "qm migrate" ?
>
> something like:
>
> qm migrate <vmid> <target> --virtio0 local:raw --virtio1 nfs:qcow2
> --virtio3 rbd:
>
> 1) if targethost = sourcehost , then we only migrate storage
>
> 2) if targethost != sourcehost, we migrate the vm + migrate 
> storage(with nbd)
>
>
> what do you think ? Does it make sense ?
>
>
> 1) should be easy to add on top of my clones patches
>
> 2) require a little more work to implement nbd
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
> !DSPAM:50f7b07f130919021075049!

-- 
Hilsen/regards
Michael Rasmussen



More information about the pve-devel mailing list