From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60178) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RAl4y-0005z6-3b for qemu-devel@nongnu.org; Mon, 03 Oct 2011 12:09:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RAl4x-0006vd-5y for qemu-devel@nongnu.org; Mon, 03 Oct 2011 12:09:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50391) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RAl4w-0006vQ-PI for qemu-devel@nongnu.org; Mon, 03 Oct 2011 12:09:19 -0400 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 p93G9HDW017003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 3 Oct 2011 12:09:17 -0400 From: Federico Simoncelli Date: Mon, 3 Oct 2011 16:09:01 +0000 Message-Id: <1317658142-21383-1-git-send-email-fsimonce@redhat.com> Subject: [Qemu-devel] New option for snapshot_blkdev to avoid image creation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: abaron@redhat.com, dlaor@redhat.com In some situations might be useful to let qemu use an image that was prepared for a live snapshot. The advantage is that creating the snapshot file outside of the qemu process we can use the whole range of options provided by the format (eg for qcow2: encryption, cluster_size and preallocation). It is also possible to pre-set a relative path to the backing file (now it is created by default as absolute path). In the long run it can also avoid the danger of reimplementing qemu-img inside qemu (if we wanted to expose such options when a snapshot is requested). -- Federico.