From: "Halsey Pian" <halsey.pian@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Security for QCOW2 format
Date: Sat, 8 Nov 2014 00:32:41 +0800 [thread overview]
Message-ID: <000001cffaa8$7cd57f50$76807df0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 5697 bytes --]
next reply other threads:[~2014-11-07 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 16:32 Halsey Pian [this message]
2014-11-08 7:01 ` [Qemu-devel] Security for QCOW2 format Fam Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001cffaa8$7cd57f50$76807df0$@gmail.com' \
--to=halsey.pian@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.