From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56953)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1XCc6s-0005tM-L5
	for qemu-devel@nongnu.org; Wed, 30 Jul 2014 18:12:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1XCc6l-0007TZ-5c
	for qemu-devel@nongnu.org; Wed, 30 Jul 2014 18:12:34 -0400
Received: from mx.beyond.pl ([92.43.117.49]:38662)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1XCc6k-0007Sa-Uj
	for qemu-devel@nongnu.org; Wed, 30 Jul 2014 18:12:27 -0400
Message-ID: <53D96DBE.2040700@beyond.pl>
Date: Thu, 31 Jul 2014 00:12:14 +0200
From: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= <m.gibula@beyond.pl>
MIME-Version: 1.0
References: <CABYiri8_naTkFgVJEwy9O52gRYHTVGwo-6sH-r+0FOFPf0Zm8w@mail.gmail.com>	<CABYiri_Jb+cAty591-cmqsgxbZne-9BZeDwDOFdAm1gaKtpgzQ@mail.gmail.com>	<20140715210948.GA20036@amt.cnet>	<CABYiri9Z3iDPn1JRSR-_x4SntBZms3yQPaChSbyRFAi2W9yScw@mail.gmail.com>	<53C5A4C9.80609@redhat.com>	<CABYiri9MigkURgV273kVjhnYxLz_WnQtsZzToy531vY0cjiGkQ@mail.gmail.com>	<20140716011634.GA30717@amt.cnet>	<CABYiri96UbyO238wYKz9OC5Tn69jZ7XdaoEX1A2ucbPTrbA1tg@mail.gmail.com>	<20140716115229.GA7741@amt.cnet>	<CABYiri9mNpaY35EVGLTjR6c7SkY2HgttpN_3NihFy2jcOQ9raQ@mail.gmail.com>	<CABYiri_vDLR=PATk1Lb99nDcJf4Q-yajayyMR1Tuv6bfwVUjgQ@mail.gmail.com>	<53C6EE7C.60702@beyond.pl>	<CABYiri8HdQhsoaf2=FHLG+KyrNj05FT015bNcEk9ngH	6Dxo7dQ@mail.gmail.com>	<53C79C41.4000800@beyond.pl>	<53C7B989.9000203@beyond.pl>	<CABYiri-aeP=0NcKaoaa=_au9sruvxnPVNri_Vy2KxKFHRj2fUw@mail.gmail.com>	<53C7CEE5.4080006@beyond.pl>	<53C8DF68.5040705@redhat.com>
	<53D7D2B5.8060500@redhat.com>	<53D8DEE1.8080905@beyond.pl>
	<53D8F546.4010803@redhat.com>
In-Reply-To: <53D8F546.4010803@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] latest rc: virtio-blk hangs forever after migration
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>, Andrey Korolyov <andrey@xdel.ru>
Cc: Amit Shah <amit.shah@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>, Fam Zheng <famz@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

W dniu 2014-07-30 15:38, Paolo Bonzini pisze:
> Il 30/07/2014 14:02, Marcin Gibu=C5=82a ha scritto:
>> without it:

s/without/with/ of course...

>> called do_kvm_cpu_synchronize_state_always
>> called do_kvm_cpu_synchronize_state_always
>> called do_kvm_cpu_synchronize_state: vcpu not dirty, getting registers
>> called do_kvm_cpu_synchronize_state: vcpu not dirty, getting registers
>> shutting down
>>
>> So it's probably about 2 from your list ("the next call to
>> do_kvm_cpu_synchronize_state will do kvm_arch_get_registers").
>
> Can you dump *env before and after the call to kvm_arch_get_registers?

Yes, but it seems they are equal - I used memcmp() to compare them. Is=20
there any other side effect that cpu_synchronize_all_states() may have?

The second caller of this function is qemu_savevm_state_complete().

--=20
mg