From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yoshiaki Tamura Subject: Re: [RFC PATCH 00/20] Kemari for KVM v0.1 Date: Mon, 26 Apr 2010 19:44:18 +0900 Message-ID: <4BD56E82.2020906@lab.ntt.co.jp> References: <1271829445-5328-1-git-send-email-tamura.yoshiaki@lab.ntt.co.jp> <4BD19F9C.2000102@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, aliguori@us.ibm.com, mtosatti@redhat.com, ohmura.kei@lab.ntt.co.jp, yoshikawa.takuya@oss.ntt.co.jp To: Avi Kivity Return-path: Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]:50396 "EHLO tama500.ecl.ntt.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751893Ab0DZKog (ORCPT ); Mon, 26 Apr 2010 06:44:36 -0400 In-Reply-To: <4BD19F9C.2000102@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > On 04/21/2010 08:57 AM, Yoshiaki Tamura wrote: >> Kemari starts synchronizing VMs when QEMU handles I/O requests. >> Without this patch VCPU state is already proceeded before >> synchronization, and after failover to the VM on the receiver, it >> hangs because of this. > > We discussed moving the barrier to the actual output device, instead of > the I/O port. This allows you to complete the I/O transaction before > starting synchronization. > > Does it not work for some reason? Sorry, I've just started working on that. I've posted this series to share what I have done so far. Thanks for looking.