qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] latest rc: virtio-blk hangs forever after migration


From: Andrey Korolyov
Subject: Re: [Qemu-devel] latest rc: virtio-blk hangs forever after migration
Date: Fri, 22 Aug 2014 23:51:53 +0400

On Fri, Aug 22, 2014 at 11:05 PM, Marcelo Tosatti <address@hidden> wrote:
> On Fri, Aug 22, 2014 at 04:05:07PM -0300, Marcelo Tosatti wrote:
>> On Fri, Aug 22, 2014 at 10:39:38PM +0400, Andrey Korolyov wrote:
>> > On Fri, Aug 22, 2014 at 9:45 PM, Marcelo Tosatti <address@hidden> wrote:
>> > > On Fri, Aug 22, 2014 at 08:44:53PM +0400, Andrey Korolyov wrote:
>> > >> >
>> > >> > I`m running 3.10, so patches are not here, will try 3.16 soon. Even if
>> > >> > problem will be fixed, it still will be specific for 2.1, earlier
>> > >> > releases working well and I`ll bisect at a time.
>> > >>
>> > >> Thanks, using 3.16 helped indeed. Though the bug remains as is at 2.1
>> > >> on LTS 3.10, should I find the breaking commit, or it is better to
>> > >> backport kvm subsystem changes related to apic to 3.10?
>> > >
>> > > Andrey,
>> > >
>> > > Can you try the patchset (which includes cpu_clean_all_dirty) please?
>> > > It should be equivalent to your proposed patch.
>> > >
>> > >
>> >
>> >
>> > Just checked case for Windows, bug is still here (twelve continuous
>> > ping-pong migrations between two hosts). Also there is very weird
>> > observation that the if VM stalled, password window renders in a
>> > cripple way just after connection when no VNC region refreshes are
>> > made yet by mouse, vm-is-alive case rendering after-c-a-d prompt
>> > properly. Probably it`ll be easier to check behaviour against Paolo`
>> > patchset for RH kernel, though I`m still in progress with cutting out
>> > the rest to adapt them on top of bare 3.10, for ones with access to
>> > git log it should be easier :)
>>
>> Argh i forgot cpu_sync_all_states. Will resend shortly.
>
> Well, can you add cpu_synchronize_all_states() before
> the cpu_clean_all_dirty() call and retry?
>
> Sorry.
>

Still nope, and libvirtd-receiver crashed eventually during test, lol.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]