|
From: | Halsey Pian |
Subject: | [Qemu-devel] Security for QCOW2 format |
Date: | Sat, 8 Nov 2014 00:32:41 +0800 |
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 |
[Prev in Thread] | Current Thread | [Next in Thread] |