From: walt <w41ter@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: snapshot vs COW?
Date: Sun, 14 Dec 2008 14:07:31 -0800 [thread overview]
Message-ID: <gi4034$kl2$1@ger.gmane.org> (raw)
In-Reply-To: <20081214183509.GB2995@networkno.de>
Thiemo Seufer wrote:
> Jamie Lokier wrote:
>> walt wrote:
>>> 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.
>> Aieee! I use COW instead of snapshots in my management scripts,
>> because snapshots are harder to manage.
>>
>> Is the COW brokenness documented? What version did it start being broken?
> Cow2 is broken in the 0.9.1 release, it was fixed shortly afterwards.
> The symptom was corruption of the image when it grew beyond 4 GB...
Glad to hear it, thanks for the update. That means that the fix is
already in the kvm git repository?
prev parent reply other threads:[~2008-12-14 22:07 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
2008-12-14 18:12 ` Jamie Lokier
2008-12-14 18:35 ` Thiemo Seufer
2008-12-14 22:07 ` walt [this message]
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='gi4034$kl2$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).