[pve-devel] [PATCH] migrate : add nocheck for resume

[Alexandre DERUMIER]

>>Another possibility could be to do the move on the target node

also another possiblity, but more complex,

is to not start the target vm as paused, and do the config file move inside qemu code, 
in the source vm at the end of migration.


(currently, we use pause/resume to get some kind of atomically to be sure that the config file is
 always on the host with running process)



----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "dietmar" <dietmar at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 15 Octobre 2015 09:09:20
Objet: Re: [pve-devel] [PATCH] migrate : add nocheck for resume

>>I am not sure about that, because it break the basic assumption that only 
>>the owner node is allowed to do such actions. 
>> 
>>Another way to solve it would be a simple loop to wait until the file arrives? 

I don't like that, because I'll increase the vm interruption time. 

Another possibility could be to do the move on the target node 


----- Mail original ----- 
De: "dietmar" <dietmar at proxmox.com> 
À: "aderumier" <aderumier at odiso.com> 
Cc: "pve-devel" <pve-devel at pve.proxmox.com> 
Envoyé: Jeudi 15 Octobre 2015 08:42:57 
Objet: Re: [pve-devel] [PATCH] migrate : add nocheck for resume 

> About my previous patch (for resume nocheck config file), I think it can still 
> apply it. 
> as we can't be sure that we don't have small replication latencies. 

I am not sure about that, because it break the basic assumption that only 
the owner node is allowed to do such actions. 

Another way to solve it would be a simple loop to wait until the file arrives? 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel