All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Bug 1662050 <1662050@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1662050] Re: qemu-img convert a overlay qcow2 image into a entire image
Date: Mon, 6 Feb 2017 12:34:07 -0600	[thread overview]
Message-ID: <41a3181b-3345-b280-afd1-6b90b51d260c@redhat.com> (raw)
In-Reply-To: <20170206031921.14255.83819.launchpad@soybean.canonical.com>

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

On 02/05/2017 09:19 PM, wayen wrote:
> 
>   I have a base image file "base.qcow2" and a delta qcow2 image file
>   "delta.qcow2" whose backing file is "base.qcow2".
>   
>   Now I use qemu-img to convert "delta.qcow2" and will get a new image
> + file "new.qcow2" which is entire and equivalent to combination of
>   "base.qcow2" and "delta.qcow2".
>   
>   In fact, i just want to convert the delta qcow2 image file and get a new
>   delta overlay qcow2 image file. So the "new.qcow2" is not what i want. I
>   have to admit that this is not bug. Could you please take this as a new
>   feature and enable qemu-img to convert images in-place?

This feature already exists.  Use:

qemu-img rebase -F $backing_fmt -b '' -f qcow2 delta.qcow2

and now delta.qcow2 will be a complete image.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2017-02-06 18:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  2:45 [Qemu-devel] [Bug 1662050] [NEW] qemu-img convert a delta qcow2 image into a complete image wayen
2017-02-06  2:54 ` [Qemu-devel] [Bug 1662050] " wayen
2017-02-06  3:19 ` [Qemu-devel] [Bug 1662050] Re: qemu-img convert a overlay qcow2 image into a entire image wayen
2017-02-06 18:34   ` Eric Blake [this message]
2017-02-07  2:12 ` wayen
2017-02-07  2:33 ` wayen
2017-02-07  3:21 ` wayen
2017-02-07 12:11 ` Thomas Huth
2017-02-08  2:04 ` wayen
2017-02-08  8:04 ` Thomas Huth
2017-02-08  8:16 ` wayen
2017-02-08 13:41   ` Eric Blake
2017-02-09  2:05 ` wayen
2017-02-13 14:13   ` Stefan Hajnoczi
2017-02-14  2:00 ` wayen
2017-02-14  2:06 ` wayen
2017-02-14  2:16 ` wayen
2017-02-14  2:17 ` wayen
2017-02-15 14:24   ` Stefan Hajnoczi
2017-04-10  2:14 ` wayen
2017-04-10  3:04   ` 858585 jemmy
2017-04-10  2:16 ` wayen
2017-04-10  5:07 ` wayen
2017-04-10  6:30   ` 858585 jemmy
2017-04-10  7:00 ` wayen
2017-06-10  4:17 ` Launchpad Bug Tracker

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=41a3181b-3345-b280-afd1-6b90b51d260c@redhat.com \
    --to=eblake@redhat.com \
    --cc=1662050@bugs.launchpad.net \
    --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.