From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43742) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrIg1-0001bY-9M for qemu-devel@nongnu.org; Thu, 12 Dec 2013 21:40:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VrIfv-0008Gs-6j for qemu-devel@nongnu.org; Thu, 12 Dec 2013 21:40:29 -0500 Received: from mx1.redhat.com ([209.132.183.28]:11019) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrIfu-0008Gm-V6 for qemu-devel@nongnu.org; Thu, 12 Dec 2013 21:40:23 -0500 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id rBD2eKq2025466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 12 Dec 2013 21:40:21 -0500 Date: Thu, 12 Dec 2013 18:40:15 -0800 From: Ian Main Message-ID: <20131213024014.GA7812@gate.mains.priv> References: <1386836626-6436-1-git-send-email-famz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1386836626-6436-1-git-send-email-famz@redhat.com> Subject: Re: [Qemu-devel] [PATCH v7 00/10] Drop in_use from BlockDriverState and enable point-in-time snapshot exporting over NBD List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng Cc: kwolf@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org, rjones@redhat.com, stefanha@redhat.com, pbonzini@redhat.com On Thu, Dec 12, 2013 at 04:23:36PM +0800, Fam Zheng wrote: > This series adds for point-in-time snapshot NBD exporting based on > blockdev-backup (variant of drive-backup with existing device as target). > > We get a thin point-in-time snapshot by COW mechanism of drive-backup, and > export it through built in NBD server. The steps are as below: > > 1. (SHELL) qemu-img create -f qcow2 BACKUP.qcow2 > > (Alternatively we can use -o backing_file=RUNNING-VM.img to omit explicitly > providing the size by ourselves, but it's risky because RUNNING-VM.qcow2 is > used r/w by guest. Whether or not setting backing file in the image file > doesn't matter, as we are going to override the backing hd in the next > step) > > 2. (QMP) blockdev-add backing=source-drive file.driver=file file.filename=BACKUP.qcow2 id=target0 if=none driver=qcow2 > > (where source-drive is the running BlockDriverState name for > RUNNING-VM.img. This patch implements "backing=" option to override > backing_hd for added drive) > > 3. (QMP) blockdev-backup device=source-drive sync=none target=target0 > > (this is the QMP command introduced by this series, which use a named > device as target of drive-backup) > > 4. (QMP) nbd-server-add device=target0 > > When image fleecing done: > > 1. (QMP) block-job-complete device=source-drive If you do another revision, this should be block-job-cancel. Ian