From: Charles Duffy <Charles_Duffy@messageone.com>
To: kvm@vger.kernel.org
Subject: Re: Best choice for copy/clone/snapshot
Date: Wed, 13 May 2009 12:19:11 -0500 [thread overview]
Message-ID: <4A0B010F.8000602@messageone.com> (raw)
In-Reply-To: <1242229787.4004.9.camel@corn.betterworld.us>
Ross Boylan wrote:
> Or do you mean I should back each virtual disk with an LVM volume?
Yes, this option is what was meant.
> 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 ?
While new versions of qcow2 have some extensions that let the
last-written sector be tracked for use on device-backed partitions, the
expectation is that you'll (really) just use the raw partition; qcow2
more than takes back the performance gain from getting your host
filesystem out of the loop.
> I'm not sure how growing the logical
> volume would interact with qcow...
Right -- folks doing this route go raw rather than qcow, so it's just a
matter of resizing the partitions / filesystems within the guest.
next prev parent reply other threads:[~2009-05-13 17:19 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
2009-05-13 17:19 ` Charles Duffy [this message]
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=4A0B010F.8000602@messageone.com \
--to=charles_duffy@messageone.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