|
From: | Marcin Gibuła |
Subject: | Re: [Qemu-devel] latest rc: virtio-blk hangs forever after migration |
Date: | Thu, 31 Jul 2014 00:12:14 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
W dniu 2014-07-30 15:38, Paolo Bonzini pisze:
Il 30/07/2014 14:02, Marcin Gibuła 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 there any other side effect that cpu_synchronize_all_states() may have?
The second caller of this function is qemu_savevm_state_complete(). -- mg
[Prev in Thread] | Current Thread | [Next in Thread] |