public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: making snapshots with raw devices? and some general snapshot thoughts
Date: Wed, 25 Feb 2009 14:20:42 +0100	[thread overview]
Message-ID: <49A545AA.60508@wpkg.org> (raw)

Is it possible to make snapshots when using raw devices (i.e. disk, 
partition, LVM volume) as guest's disk image?

According to documentation[1] (and some tests I made) it is only 
possible with qcow2 images. Which makes it very inflexible:

- one is forced to use a potentially slower file access
- one can't use the benefits of i.e. iSCSI disk access, SAN etc.


Also, according to the documentation, "VM snapshots are snapshots of the 
complete virtual machine including CPU state, RAM, device state and the 
content of all the writable disks".

Which leads to another observation: in some situations what one really 
needs is to "pause" execution of guest from within the host (i.e. 
because you want to shutdown or reboot the host due to a kernel or 
hardware upgrade).
After all changes on host are done, "guest" should be resumed without 
even knowing it was paused (most likely it will loose network connections).

This is how it's done with Xen or other virtualization solutions - they 
only save RAM, CPU, device state to a separate file; they don't save the 
content of all disks, because it's normally not needed for "pausing" guests.

Is it possible to do it with KVM?



[1] http://bellard.org/qemu/qemu-doc.html#SEC18


-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2009-02-25 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 13:20 Tomasz Chmielewski [this message]
2009-02-25 14:10 ` making snapshots with raw devices? and some general snapshot thoughts Javier Guerra
2009-02-25 14:31   ` Tomasz Chmielewski
2009-02-25 14:33     ` Javier Guerra
2009-02-25 15:44 ` Anthony Liguori
2009-02-25 16:11   ` Tomasz Chmielewski

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=49A545AA.60508@wpkg.org \
    --to=mangoo@wpkg.org \
    --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