>>Sound easy enough. And that solves the whole problem? I solve 99,99%. with this zait's safe to launch the target vm without -S
last thing, is that just after end of the migration, the source kvm process is in pause (no more acess to disk), but we stop it at the end of the phase 3. So, if source host crash, it's not a problem. If proxmox task crash (after the migration and before the stop), we can have a phantom kvm process on source node, but doing nothing Note that is already like this now. ----- Mail original ----- De: "Dietmar Maurer" <diet...@proxmox.com> À: "Alexandre DERUMIER" <aderum...@odiso.com>, "Michael Rasmussen" <m...@datanom.net> Cc: pve-devel@pve.proxmox.com Envoyé: Samedi 23 Février 2013 14:55:17 Objet: RE: [pve-devel] successfull migration but failed resume > Maybe can we hack qemu, and make the file rename from qemu, at the end of > the migration ? > Dietmar, what do you think about this ? Sound easy enough. And that solves the whole problem? _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
