All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Prof. Dr. Michael Schefczyk" <michael@schefczyk.net>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] "File too large" error from "qemu-img snapshot" (was Re: AW: Bug Repoting Directions Request)
Date: Tue, 25 Nov 2014 12:34:05 +0100	[thread overview]
Message-ID: <20141125113405.GD4641@noname.redhat.com> (raw)
In-Reply-To: <2A6E6B95B6E5C146ACE8440760E58185BDC4FF51@EXCHANGESERVER.schefczyk.local>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

Am 22.11.2014 um 18:02 hat Prof. Dr. Michael Schefczyk geschrieben:
> Dear All,
> 
> after some trying, my impression is that the following steps do work with plain Centos 7:
> 
> virsh snapshot-create-as VM backsnap
> qemu-img convert -f qcow2 -s backsnap -O qcow2 VM.img backup.img
> virsh snapshot-delete VM backsnap
> 
> Am I on the right track with these commands?

I won't tell you that you're bound to break your image with this
sequence, because chances are that you won't break it. (In practice,
this happens to work in most cases, because the essential snapshot
metadata generally isn't written to without explicit user actions on
that snapshot.)

But you're violating the rule of "one writer or many readers", so as far
as qemu is concerned, we won't be careful to avoid breaking this setup.
Don't blame us if it fails one day.

With the QMP solutions (either drive-backup or snapshot/commit) you're
using official APIs, so I'd encourage you to use these.

Kevin

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-11-25 11:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 10:36 Bug Repoting Directions Request Prof. Dr. Michael Schefczyk
2014-11-19 10:59 ` Paolo Bonzini
     [not found]   ` <2A6E6B95B6E5C146ACE8440760E58185BDC31C30@EXCHANGESERVER.schefczyk.local>
2014-11-19 11:41     ` [Qemu-devel] "File too large" error from "qemu-img snapshot" (was Re: AW: Bug Repoting Directions Request) Paolo Bonzini
2014-11-19 11:48       ` Prof. Dr. Michael Schefczyk
2014-11-19 11:53         ` Paolo Bonzini
2014-11-19 12:07           ` Prof. Dr. Michael Schefczyk
2014-11-19 14:54             ` Paolo Bonzini
2014-11-19 15:43               ` Eric Blake
2014-11-19 17:32                 ` Prof. Dr. Michael Schefczyk
2014-11-19 18:13                   ` Eric Blake
2014-11-22 17:02                     ` Prof. Dr. Michael Schefczyk
2014-11-24 11:52                       ` Paolo Bonzini
2014-11-25 11:34                       ` Kevin Wolf [this message]
2014-11-25 11:49                         ` Prof. Dr. Michael Schefczyk
2014-11-24 10:32                     ` Kashyap Chamarthy
2014-11-19 14:05       ` Max Reitz

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=20141125113405.GD4641@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=michael@schefczyk.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.