All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: anthony@codemonkey.ws
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 3/4] Documentation: Warn against qemu-img on active image
Date: Fri, 17 Aug 2012 21:25:07 +0200	[thread overview]
Message-ID: <1345231508-7633-4-git-send-email-kwolf@redhat.com> (raw)
In-Reply-To: <1345231508-7633-1-git-send-email-kwolf@redhat.com>

People have repeatedly expected that you can do things like snapshotting
an image with qemu-img while a qemu instance is running. Maybe we need
to consider locking the files while they are in use, but having a
warning in the qemu-img manpage is doable for 1.2 and can't hurt anyway.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
 qemu-img.texi |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/qemu-img.texi b/qemu-img.texi
index 77c6d0b..77b2c47 100644
--- a/qemu-img.texi
+++ b/qemu-img.texi
@@ -4,6 +4,14 @@ usage: qemu-img command [command options]
 @c man end
 @end example
 
+@c man begin DESCRIPTION
+qemu-img allows you to create, convert and modify images offline. It can handle
+all image formats supported by QEMU.
+
+@b{Warning:} Never use qemu-img to modify images in use by a running virtual
+machine or any other process; this may destroy the image.
+@c man end
+
 @c man begin OPTIONS
 
 The following commands are supported:
-- 
1.7.6.5

  parent reply	other threads:[~2012-08-17 19:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 19:25 [Qemu-devel] [PULL 0/4] Block patches for 1.2-rc1 Kevin Wolf
2012-08-17 19:25 ` [Qemu-devel] [PATCH 1/4] vmdk: Fix header structure Kevin Wolf
2012-08-17 19:25 ` [Qemu-devel] [PATCH 2/4] vmdk: Read footer for streamOptimized images Kevin Wolf
2012-08-17 19:25 ` Kevin Wolf [this message]
2012-08-17 19:25 ` [Qemu-devel] [PATCH 4/4] virtio-blk: hide VIRTIO_BLK_F_CONFIG_WCE from old machine types Kevin Wolf
2012-08-20 12:46   ` Paolo Bonzini
2012-08-20 12:51     ` 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=1345231508-7633-4-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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.