From: walt <w41ter@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: snapshot vs COW?
Date: Fri, 12 Dec 2008 05:25:44 -0800 [thread overview]
Message-ID: <ghtoop$jta$1@ger.gmane.org> (raw)
In-Reply-To: <fdaac4d50812111917n47c27f5atf36b81f7c40c620e@mail.gmail.com>
Jun Koi wrote:
> Hi,
>
> From what I see, both snapshot and COW features can be used to try
> some changes on the file image before we the change back to the
> original image.
>
> But what is the advantages of snapshot over COW, and in which case we
> should use snapshot, but not COW? Vice verse, when COW is more
> appropriate?
>
> Many thanks,
> Jun
COW is a nice feature but it is currently broken, so don't use it
until it gets fixed. When you commit any changes your backing file
will be corrupted.
next prev parent reply other threads:[~2008-12-12 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 3:17 [Qemu-devel] snapshot vs COW? Jun Koi
2008-12-12 3:18 ` [Qemu-devel] " Jun Koi
2008-12-12 13:25 ` walt [this message]
2008-12-14 18:12 ` Jamie Lokier
2008-12-14 18:35 ` Thiemo Seufer
2008-12-14 22:07 ` walt
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='ghtoop$jta$1@ger.gmane.org' \
--to=w41ter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).