When i try to cancel a running migration with qemu git i get a segfault.
BT:
(gdb) bt
#0 _wordcopy_bwd_aligned (dstp=140051233112024, srcp=140051233112016,
len=529920) at wordcopy.c:298
#1 0x7f61dd7c86da in *__GI_memmove (dest=0x7f6037bf5010,
src=, len=38118264) at memmove.c:99
#2 0x
Il 29/12/2012 16:19, Stefan Priebe ha scritto:
>>
>>
>> I suppose it will be between 05e72dc5812a9f461fc2c606dff2572909eafc39
>> and aa723c23147e93fef8475bd80fd29e633378c34d.
>>
>> Probably at 2dddf6f4133975af62e64cb6406ec1239491fa89, which was supposed
>> to be placed before switching to the migra
Am 29.12.2012 15:58, schrieb Paolo Bonzini:
Il 29/12/2012 15:05, Stefan Priebe ha scritto:
It starts working to me after the first 22 patches (after introducing
the new mutex and threading for writes).
And when does it break in 1.3?
I suppose it will be between 05e72dc5812a9f461fc2c606dff2572
Il 29/12/2012 15:05, Stefan Priebe ha scritto:
> Hi Paolo,
> Am 29.12.2012 15:00, schrieb Paolo Bonzini:
>>> i cherry picked that one on top of 1.3 sadly it does not help. VM halts,
>>> monitor socket is no longer available kvm process is running with 100%
>>> CPU on source side.
>>
>> Can you plea
Hi Paolo,
Am 29.12.2012 15:00, schrieb Paolo Bonzini:
i cherry picked that one on top of 1.3 sadly it does not help. VM halts,
monitor socket is no longer available kvm process is running with 100%
CPU on source side.
Can you please test master and, if it works, bisect it in reverse?
(That is,
Il 28/12/2012 20:03, Stefan Priebe ha scritto:
> Hi Paolo,
>
> Am 28.12.2012 18:53, schrieb Paolo Bonzini:
>> Il 28/12/2012 08:05, Alexandre DERUMIER ha scritto:
>>> Hi list,
>>> After discuss with Stefan Yesterday here some more info:
>>>
>>> (this is for stable qemu 1.3, it was working fine with
Hi Paolo,
Am 28.12.2012 18:53, schrieb Paolo Bonzini:
Il 28/12/2012 08:05, Alexandre DERUMIER ha scritto:
Hi list,
After discuss with Stefan Yesterday here some more info:
(this is for stable qemu 1.3, it was working fine with qemu 1.2)
The problem seem that whesettings a migrate_set_downtime
Il 28/12/2012 08:05, Alexandre DERUMIER ha scritto:
> Hi list,
> After discuss with Stefan Yesterday here some more info:
>
> (this is for stable qemu 1.3, it was working fine with qemu 1.2)
>
> The problem seem that whesettings a migrate_set_downtime to 1sec,
>
> the transfert of the vm seem to
an Priebe"
À: "qemu-devel"
Envoyé: Jeudi 27 Décembre 2012 22:54:55
Objet: [Qemu-devel] setting migrate_downtime results in halted vm
Hello list,
i'm using qemu 1.3 and migration works fine if i do not set
migrate_downtime.
If i set migrate_downtime to 1s or 0.5s or 0.3s the VM
Hello list,
i'm using qemu 1.3 and migration works fine if i do not set
migrate_downtime.
If i set migrate_downtime to 1s or 0.5s or 0.3s the VM halts immediatly
i cannot even connect to the qmp socket anymore and migration takes 5-10
minutes or never finishes.
I see high cpu usage on sour
10 matches
Mail list logo