From: dmc <dmc@filteredperception.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFE- snapshot data storage location configurable
Date: Sat, 11 Aug 2007 13:41:14 -0500 [thread overview]
Message-ID: <46BE02CA.4000306@filteredperception.org> (raw)
In-Reply-To: <fb249edb0708110916i238c440ej54816ba5ada72d2a@mail.gmail.com>
andrzej zaborowski wrote:
> On 01/08/07, dmc <dmc@filteredperception.org> wrote:
>> I have a pretty ugly patch against qemu 0.8 which allows the location of data
>> used with the -snapshot feature to be somewhere other than /var/tmp. I have a
>> use-case where I am creating many gigabytes of changes to disk in snapshot mode.
>> When 0.9 came out, I looked, but it seemed less than trivial to update my
>> patch, which was a pretty ugly hack to begin with.
>>
>> I don't suppose anybody else thinks this would be a useful feature? Or at least
>> someone who can rattle off the top of their heads the sorts of things I should
>> keep in mind while trying to put it together myself?
>>
>> A further extension, which I would like, but is also more complex to add, would
>> be the ability to specify -snapshot, _per device_.
>
> I also thought that would be useful earlier but now qcow2 overlays
> provide much better flexibility and don't litter the commandline
> syntax. I think the currently available choice between -snapshot (for
> the simplest possible use case) and qcow2 overlays (for anything more
> complex) is a perfect balance for usability and there's no need to add
> more switches.
Excellent!
Those little tidbits in the documentation ( -b flag for qemu-img create
) had completely gone under my radar. That definitely gets me
everything I want.
Thanks,
-dmc
prev parent reply other threads:[~2007-08-11 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 1:48 [Qemu-devel] RFE- snapshot data storage location configurable dmc
2007-08-05 11:18 ` J M Cerqueira Esteves
2007-08-05 19:44 ` dmc
2007-08-11 16:16 ` andrzej zaborowski
2007-08-11 18:41 ` dmc [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=46BE02CA.4000306@filteredperception.org \
--to=dmc@filteredperception.org \
--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).