From: Ross Boylan <ross@biostat.ucsf.edu>
To: Avi Kivity <avi@redhat.com>
Cc: ross@biostat.ucsf.edu, kvm@vger.kernel.org
Subject: Re: Best choice for copy/clone/snapshot
Date: Wed, 13 May 2009 08:49:47 -0700 [thread overview]
Message-ID: <1242229787.4004.9.camel@corn.betterworld.us> (raw)
In-Reply-To: <4A0A71C0.1060109@redhat.com>
Thanks for all the info. I have one follow up.
On Wed, 2009-05-13 at 10:07 +0300, Avi Kivity wrote:
>
> > As I install software onto a system I want to preserve its
> state--just
> > the disk state---at various points so I can go back. What is the
> best
> > way to do this?
> >
>
> LVM snapshots. Read up on the 'lvcreate -s' command and option.
I may have been unclear. I meant as I install software on the VM.
Since some of them are running Windows, they can't do LVM. I am running
LVM on my host Linux system.
Or are you suggesting that I put the image files on a snapshottable
partition? Over time the snapshot seems likely to accumulate a lot of
original sectors that don't involve the disk image I care about.
Or do you mean I should back each virtual disk with an LVM volume? That
does seem cleaner; I've just been following the docs and they use
regular files. They say I can't just use a raw partition, but maybe
kvm-img -f qcow2 /dev/MyVolumeGroup/Volume10 ?
Does that give better performance? The one drawback I see is that I'd
have to really take the space I wanted, rather than having it only
notionally reserved for a file. I'm not sure how growing the logical
volume would interact with qcow...
Ross
next prev parent reply other threads:[~2009-05-13 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 1:08 Best choice for copy/clone/snapshot Ross Boylan
2009-05-13 7:07 ` Avi Kivity
2009-05-13 15:49 ` Ross Boylan [this message]
2009-05-13 17:19 ` Charles Duffy
2009-05-14 9:16 ` Avi Kivity
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=1242229787.4004.9.camel@corn.betterworld.us \
--to=ross@biostat.ucsf.edu \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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