From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tde7E-0004u4-6Y for qemu-devel@nongnu.org; Wed, 28 Nov 2012 04:39:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tde77-0001lz-83 for qemu-devel@nongnu.org; Wed, 28 Nov 2012 04:39:36 -0500 Received: from e28smtp04.in.ibm.com ([122.248.162.4]:51165) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tde76-0001lV-Jf for qemu-devel@nongnu.org; Wed, 28 Nov 2012 04:39:29 -0500 Received: from /spool/local by e28smtp04.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 28 Nov 2012 15:09:23 +0530 Received: from d28av03.in.ibm.com (d28av03.in.ibm.com [9.184.220.65]) by d28relay04.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qAS9dKv964552968 for ; Wed, 28 Nov 2012 15:09:20 +0530 Received: from d28av03.in.ibm.com (loopback [127.0.0.1]) by d28av03.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qAS9dKm6009019 for ; Wed, 28 Nov 2012 20:39:20 +1100 Message-ID: <50B5DBC2.9060101@linux.vnet.ibm.com> Date: Wed, 28 Nov 2012 17:39:14 +0800 From: Wenchao Xia MIME-Version: 1.0 References: <1353488464-82756-1-git-send-email-dietmar@proxmox.com> <50B4916D.40909@linux.vnet.ibm.com> <24E144B8C0207547AD09C467A8259F7557832A89@lisa.maurer-it.com> In-Reply-To: <24E144B8C0207547AD09C467A8259F7557832A89@lisa.maurer-it.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 1/5] RFC: Efficient VM backup for qemu (v1) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dietmar Maurer Cc: "kwolf@redhat.com" , "qemu-devel@nongnu.org" 于 2012-11-27 18:37, Dietmar Maurer 写道: >> Just want to confirm something to understand it better: >> you are backing up the block image not including VM memory state right? I >> am considering a way to do live Savevm including memory and device state, >> so wonder if you already had a solution for it. > > Yes, I have already code for that. > > Does those code for VM memory and device state lively save/restore included in this patch serials? I quickly reviewed the patches but did not found a hook to save VM memory state? Hope you can enlight me your way, my thoughts is do live migration into qcow2 file, but your code seems not touched qcow2 images. -- Best Regards Wenchao Xia