From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC PATCH 00/20] Kemari for KVM v0.1 Date: Fri, 23 Apr 2010 16:24:44 +0300 Message-ID: <4BD19F9C.2000102@redhat.com> References: <1271829445-5328-1-git-send-email-tamura.yoshiaki@lab.ntt.co.jp> 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: Yoshiaki Tamura Return-path: Received: from mx1.redhat.com ([209.132.183.28]:62345 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755777Ab0DWNYy (ORCPT ); Fri, 23 Apr 2010 09:24:54 -0400 In-Reply-To: <1271829445-5328-1-git-send-email-tamura.yoshiaki@lab.ntt.co.jp> Sender: kvm-owner@vger.kernel.org List-ID: 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? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.