[pve-devel] successfull migration but failed resume

[Stefan Priebe]

Hi,

what is the problem / disadvantage of this way:

1.) don't use -S so the VM starts directly after being migrated (we 
minimize downtime by may be 1s for the ssh resume stuff)

2.) we move the config file at the beginning of the migration

3.) if the source host crashes while migration the source kvm process is 
dead anyways so starting on the new target won't be a problem

4.) if the target host crashes while migrating the source host will 
detect this and abort the migration + move the config back.

Greets,
Stefan

Am 24.02.2013 13:48, schrieb Stefan Priebe:
> Hi Alexandre,
> Am 24.02.2013 09:34, schrieb Alexandre DERUMIER:
>>>> I've seen this sometimes. Is there any way to see how the output of the
>>>> ssh command was?
>> Stefan, when you have this error, do you see a "resume task" in
>> pve-manager task list ?
>
> Yes i have a resume task and this task show status OK. But the migration
> task says failed.
>
> Stefan
>
>>
>> ----- Mail original -----
>>
>> De: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag>
>> À: pve-devel at 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 at 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 at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>