From: Markus Armbruster <armbru@redhat.com>
To: Iordan Iordanov <iordan@cdf.toronto.edu>
Cc: kvm@vger.kernel.org
Subject: Re: differencing disks support
Date: Thu, 09 Jun 2011 08:24:28 +0200 [thread overview]
Message-ID: <m3lixbldyb.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <4DEFD70E.4020209@cdf.toronto.edu> (Iordan Iordanov's message of "Wed, 08 Jun 2011 16:09:50 -0400")
Iordan Iordanov <iordan@cdf.toronto.edu> writes:
> Does KVM support or plan to support differencing disks (where there is
> a read-only source disk, and each person running a virtual machine can
> save block-level changes that their virtual machine is making to the
> disk in a separate "differencing" image)?
>
> If so, can somebody suggest how I may make use of this feature
> (i.e. building the newest version from source, and any other
> requirements).
Check out image format qcow2.
LVM snapshots were already mentioned.
prev parent reply other threads:[~2011-06-09 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 20:09 differencing disks support Iordan Iordanov
2011-06-08 20:33 ` Dan VerWeire
2011-06-09 6:24 ` Markus Armbruster [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=m3lixbldyb.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=iordan@cdf.toronto.edu \
--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