From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37992)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1WzXHf-0002hV-4D
	for qemu-devel@nongnu.org; Tue, 24 Jun 2014 16:25:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1WzXHV-0002ql-S4
	for qemu-devel@nongnu.org; Tue, 24 Jun 2014 16:25:38 -0400
Received: from mail-we0-x22b.google.com ([2a00:1450:400c:c03::22b]:40296)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1WzXHV-0002qY-7j
	for qemu-devel@nongnu.org; Tue, 24 Jun 2014 16:25:29 -0400
Received: by mail-we0-f171.google.com with SMTP id q58so946637wes.2
	for <qemu-devel@nongnu.org>; Tue, 24 Jun 2014 13:25:28 -0700 (PDT)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <53A9DEB3.6030603@redhat.com>
Date: Tue, 24 Jun 2014 22:25:23 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <CACtCCo_iehf=G4DZ8DjTHnP8atsUfHKLsLVkn_d1oRfFBtTfWw@mail.gmail.com>	<53A9D388.8080307@redhat.com>
	<CACtCCo-4CoJLzOhpSHKgJ__Dx_RpjHM67MV4_ph4e1DpGD25Bw@mail.gmail.com>
In-Reply-To: <CACtCCo-4CoJLzOhpSHKgJ__Dx_RpjHM67MV4_ph4e1DpGD25Bw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Live Migration with different block devices
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: Xiongzi Ge <gexxx132@umn.edu>
Cc: qemu-devel@nongnu.org

Il 24/06/2014 21:55, Xiongzi Ge ha scritto:
> Hi Paolo,
>
> I am trying to do migration with two different block devices in the
> source and destination hosts.  For example, in the source the data in
> /dev/vda are  'aaaaa'. The guest has a cache. These data are cached.  In
> the other host, the data in this device are 'bbbbb'.

Again, what you are doing is invalid.  The point of migration is to have 
the same thing running on the source and destination, including disk data.

> If we do migration, I want the  guest vm recognize this change.

This is not _what_ you want to do.  This is _how_ you want to do it.

(Example: you eat a big mac.  _What_ you want to do is not being hungry. 
  _How_ you want to do it is going at McDonald's and grabbing a 
sandwich.  Similar to your migration example, there's probably a better 
way to achieve your objective).

So, why do you want data to change upon migration?

> How does qemu deal with the cache data?  Thanks.

It's not QEMU that's caching data, it's the guest.  There's nothing that 
QEMU can do about it.

Paolo