public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: Peter Doherty <doherty@hkl.hms.harvard.edu>
Cc: kvm@vger.kernel.org
Subject: Re: disk image snapshot functionality
Date: Wed, 29 Sep 2010 15:07:23 +0900	[thread overview]
Message-ID: <4CA2D79B.5010407@oss.ntt.co.jp> (raw)
In-Reply-To: <0CDD4EAF-97E9-4718-A106-2634D891C5CF@hkl.hms.harvard.edu>

Hi,

(2010/09/29 5:24), Peter Doherty wrote:
> Hi,
>
> I'm using Centos5.5 on the host, and the KVM that's available in the repos. I'm using linux VMs too. My disk images are qcow2 files.
> Here's what I want:
> To be able to, on the host, create a snapshot of the guest's disk image, without shutting down the guest, so that I can then restore back to a point in time for the guest.

Yesterday, I heard a similar desire at the Virtualization End User Discussion @ LinuxCon Japan.

What you want to do is:
   - taking the whole VM disk image snapshot
     or
   - just taking specific partition's image?

Generally speaking, taking the whole VM disk image snapshot without breaking
guest side consistency seems difficult.

Even though you restrict to a specific partition, you need to guarantee that
the file system is in an appropriate state.


Anybody has better ideas?

   Takuya


> I thought I could do this with the qcow2 images.
> I've used:
> qemu-img snapshot -c snapname disk_image.qcow2
> to create the snapshot.
>
> It doesn't work. The snapshots claim to be created, but if I shut down the guest, apply the snapshot
> ( qemu-img snapshot -a snapname disk_image.qcow2 )
> the guest either:
> a.) no longer boots (No bootable disk found)
> b.) boots, but is just how it was when I shut it down (it hasn't reverted back to what it was like when the snapshot was made)
>
>
> It makes no sense. I can sometimes apply the first snapshot, and it has worked...but subsequent snapshots are a no go.
> One thing that is suspicious is that the VM SIZE and CLOCK are zero:
> # qemu-img snapshot -l test1.qcow2
> Snapshot list:
> ID TAG VM SIZE DATE VM CLOCK
> 1 with100mb 0 2010-09-28 11:48:23 00:00:00.000
> 2 with200mb 0 2010-09-28 11:50:53 00:00:00.000
> 3 with300mb 0 2010-09-28 11:52:49 00:00:00.000
> 4 whenoff 0 2010-09-28 11:56:41 00:00:00.000
>
>
> # /usr/libexec/qemu-kvm --help
> QEMU PC emulator version 0.9.1 (kvm-83-maint-snapshot-20090205), Copyright (c) 2003-2008 Fabrice Bellard
>
>
> I can't find much info about using qcow2 images when I search. Any help would be appreciated.
>
> Thanks.
>
> Peter
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2010-09-29  6:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 20:24 disk image snapshot functionality Peter Doherty
2010-09-29  6:07 ` Takuya Yoshikawa [this message]
2010-09-29  8:39 ` Stefan Hajnoczi
2010-09-29 14:35   ` Peter Doherty
2010-09-30  8:31     ` Stefan Hajnoczi
2010-09-30 13:49       ` Peter Doherty
2010-09-30 15:28         ` Stefan Hajnoczi

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=4CA2D79B.5010407@oss.ntt.co.jp \
    --to=yoshikawa.takuya@oss.ntt.co.jp \
    --cc=doherty@hkl.hms.harvard.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