[pve-devel] migration problems since qemu 1.3

[Alexandre DERUMIER]

>>Yes. It works fine with NEWLY started VMs but if the VMs are running 
>>more than 1-3 days. It stops working and the VMs just crahs during 
>>migration. 
Maybe vm running since 1-3 days,have more memory used, so I take more time to live migrate.

Does it crash at start of the migration ? or in the middle of the migration ?

what is your vm conf ? (memory size, storage ?)

I'll try to do tests today



----- Mail original ----- 

De: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Jeudi 20 Décembre 2012 09:54:00 
Objet: Re: [pve-devel] migration problems since qemu 1.3 

Hi Alexandre, 
Am 20.12.2012 09:50, schrieb Alexandre DERUMIER: 
> Do you mean migration between qemu-kvm 1.2 -> qemu 1.3 ? 
No. 

> or migration between qemu 1.3 -> qemu 1.3 ? 
Yes. It works fine with NEWLY started VMs but if the VMs are running 
more than 1-3 days. It stops working and the VMs just crahs during 
migration. 

> also,I don't know if it's related, but in the changelog: 
> http://wiki.qemu.org/ChangeLog/1.3 
> 
>Live Migration, Save/Restore 
> The "stop" and "cont" commands have new semantics on the destination machine during migration. Previously, the outcome depended on whether the commands were issued before or after the source connected to the destination QEMU: in particular, "cont" would fail if issued before connection, and "undo" the effect of the -S command-line option if issued after. Starting from this version, the effect of "stop" and "cont" will always take place at the end of migration (overriding the presence or absence of the -S option) and "cont" will never fail. This change should be transparent, since the old behavior was usually subject to a race condition. 
i don't see how this could result in a crash of the whole VM and a 
migration not working at all. 

Greets, 
Stefan