From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53089) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmmTJ-0002sm-SE for qemu-devel@nongnu.org; Fri, 07 Nov 2014 11:33:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XmmTA-0006Fb-Qp for qemu-devel@nongnu.org; Fri, 07 Nov 2014 11:33:13 -0500 Received: from mail-pa0-x236.google.com ([2607:f8b0:400e:c03::236]:44259) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmmTA-0006FL-Gb for qemu-devel@nongnu.org; Fri, 07 Nov 2014 11:33:04 -0500 Received: by mail-pa0-f54.google.com with SMTP id rd3so3843246pab.13 for ; Fri, 07 Nov 2014 08:33:02 -0800 (PST) Received: from JoanPC ([116.238.98.10]) by mx.google.com with ESMTPSA id ap5sm9261075pad.22.2014.11.07.08.32.55 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 07 Nov 2014 08:33:01 -0800 (PST) From: "Halsey Pian" Date: Sat, 8 Nov 2014 00:32:41 +0800 Message-ID: <000001cffaa8$7cd57f50$76807df0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01CFFAEB.8AFB0940" Content-Language: zh-cn Subject: [Qemu-devel] Security for QCOW2 format List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This is a multipart message in MIME format. ------=_NextPart_000_0001_01CFFAEB.8AFB0940 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear All, Nice to know all of you! Recently, I am reading codes of qcow2 format, in order to switch virtualization solution in my project from VMWare to KVM for more specific customization based on customer's requirements. I have one consideration related to qcow2 format in QEMU. As you know, there is all-in-one img file for QCOW2 format even if there is much original data and a number of snapshots, then maybe we would get a huge file, and maybe we cannot use this img if it is broken due to some reason/exception during long term running especially for server application. Is there a solution for this? Or is there a strategy similar to VMWare VMDK format using the structure with parent pointer to manage separate sub vmdk files? Could you give help on it? Many thanks! Best Regards Halsey Pian ------=_NextPart_000_0001_01CFFAEB.8AFB0940 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear All,

Nice to = know all of you!

Recently, I = am reading codes of qcow2 format, in order to switch virtualization = solution in my project from VMWare to KVM for more specific = customization based on customer’s requirements. =

I have one = consideration related to qcow2 format in QEMU.

As you = know, there is all-in-one img file for QCOW2 format even if there is = much original data and a number of snapshots, then maybe we would get a = huge file, and maybe we cannot use this img if it is broken due to some = reason/exception during long term running especially for server = application. Is there a solution for this? Or is there a strategy = similar to VMWare VMDK format using the structure with parent pointer to = manage separate sub vmdk files?

Could you = give help on it? Many thanks!

Best = Regards

Halsey = Pian

------=_NextPart_000_0001_01CFFAEB.8AFB0940--