qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Robert P <robp236@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU Live Snapshots / Commiting
Date: Fri, 30 Sep 2011 09:16:27 +0100	[thread overview]
Message-ID: <20110930081627.GA12834@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <CAHEq_3PadahDX-Lz_i6irGDuBOFNOs7pHn16M3tvprcTh5PcLw@mail.gmail.com>

On Thu, Sep 29, 2011 at 09:07:19PM +0200, Robert P wrote:
> Hello,
> 
> I still have a problem with the "Live Snapshot" feature of QEMU .... and
> before migrating to XEN, VMware or something similare, a quick post here:
> 
> OS: Ubuntu Natty 64bit
> 
> First, i'm starting my KVM Machine with an image like this:
> qemu-img create -f qcow2 -o backing_file=<NameOfBaseImage> <Snapshotname>
> 
> If i stop the KVM Machine later, and i commit <Snapshotname> into
> <NameOfBaseImage>, all the new changes are in the <NameOfBaseImage>.
> That would be ok.
> 
> ---
> 
> The Problem:
> 
> Actually i'm trying to create "live snapshots" periodically  while the
> machine is running, like this (host2Qemu is just a special function of mine
> (it works), to send a string to qemu-monitor).
> 
>                 host2Qemu "cont"
>                 host2Qemu "guest-agent-fsfreeze"
>                 host2Qemu "stop"
> 
>                 host2Qemu "info block"
>                 host2Qemu "snapshot_blkdev ide0-hd0 <Snapshot1 (example)>
> qcow2"
> 
>                 host2Qemu "cont"
>                 host2Qemu "guest-agent-fsthaw"
> 
> My idea is, to commit them one by one afterwards, when the KVM Machine is
> down into the BaseImage.
> 
> So, the Snapshots are beeing written, and everytime i call that function new
> data is beeing written to the new "alllocated" snapshot.
> BUT, committing of that live-snapshots fails, and i've no idea why ?!
> 
> I would commit it like that:
>  qemu-img commit -f qcow2 <Snapshot, with KVM was started first>
> qemu-img commit -f qcow2 <Snapshot1, newer>
> qemu-img commit -f qcow2 <Snapshot1, more new>
> ...
> and so on.
> 
> So in that constellation, only changes from the Snapshot, with KVM was
> started are in the Base-Image.

I'm not 100% clear that you know qemu-img commit cannot be used while
QEMU is running and has the disk image file open.  It's simply not safe
to modify the image file with qemu-img while QEMU is running.

> And another question: I have a Windows XP Guest also in KVM, but the write
> performance into the (qcow2 Image) (scp, rsync, e.g) Guest seems to be
> pretty poor - Are there any hints or is there a special Parameter to avoid
> this?
> The write Performance to a Linux Guest with a similar configuration and also
> qcow2 seems to very close to the "native" Performance.

Are you using the virtio drivers for Windows?

Stefan

  reply	other threads:[~2011-09-30  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHEq_3PLXn2F015G-GisY7MjZS-f8mgrYxHymoCX3kD+0+=B4g@mail.gmail.com>
2011-09-29 19:07 ` [Qemu-devel] QEMU Live Snapshots / Commiting Robert P
2011-09-30  8:16   ` Stefan Hajnoczi [this message]
     [not found]     ` <CAHEq_3NNj_-h5+H3P=AGoz=aTcVken2gPhcxET4dGZnWn+zAdA@mail.gmail.com>
2011-09-30 12:04       ` Stefan Hajnoczi
2011-09-30 13:46         ` Robert P
2011-09-30 14:54           ` Stefan Hajnoczi
2011-09-30 19:24             ` Robert P

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=20110930081627.GA12834@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robp236@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).