Dietmar why do we pause? Stefan
Am 22.02.2013 um 15:37 schrieb Alexandre DERUMIER <aderum...@odiso.com>: >>> root@10.255.0.20 qm resume 129 --skiplock' failed: exit code 2 >>> Feb 22 14:48:07 ERROR: migration finished with problems (duration 00:00:10) > > I have also see this bug sometimes. > > I don't know how to display the output, but the command send "cont" command > to qmp socket of migrate vm, > to resume it. So maybe it's fail to connect to qmp socket. > (maybe a retry can help ? ) > > We are starting with -S (to pause it), it is because we want to be sure to > resume it after move the config file. > > > > ----- Mail original ----- > > De: "Stefan Priebe - Profihost AG" <s.pri...@profihost.ag> > À: pve-devel@pve.proxmox.com > Envoyé: Vendredi 22 Février 2013 15:01:25 > Objet: [pve-devel] successfull migration but failed resume > > Hello, > > I've seen this sometimes. Is there any way to see how the output of the > ssh command was? > > Feb 22 14:48:05 migration speed: 819.20 MB/s - downtime 49 ms > Feb 22 14:48:05 migration status: completed > Feb 22 14:48:06 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes' > root@10.255.0.20 qm resume 129 --skiplock' failed: exit code 2 > Feb 22 14:48:07 ERROR: migration finished with problems (duration 00:00:10) > > Greets, > Stefan > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel