From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Nir Soffer <nsoffer@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Allon Mureinik <amureini@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Maor Lipchuk <mlipchuk@redhat.com>,
qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-discuss] Estimation of qcow2 image size converted from raw image
Date: Wed, 15 Feb 2017 16:11:17 +0000 [thread overview]
Message-ID: <20170215161117.GK24672@redhat.com> (raw)
In-Reply-To: <w517f4rqw27.fsf@maestria.local.igalia.com>
On Wed, Feb 15, 2017 at 05:05:04PM +0100, Alberto Garcia wrote:
> On Wed 15 Feb 2017 04:57:12 PM CET, Nir Soffer wrote:
> >>> Let's try this syntax:
> >>>
> >>> $ qemu-img query-max-size -f raw -O qcow2 input.raw
> >>> 1234678000
> >>>
> >>> As John explained, it is only an estimate. But it will be a
> >>> conservative maximum.
> >>
> >> This forces you to have an input file. It would be nice to be able to
> >> get the same information by merely giving the desired capacity e.g
> >>
> >> $ qemu-img query-max-size -O qcow2 20G
> >
> > Without a file, this will have to assume that all clusters will be
> > allocated.
>
> ...and that there are no internal snapshots. I'm not sure if this is
> very useful in general.
As long as the caveat is documented it is fine. Internal snapshots are
often completely ignored by apps since they have many downsides compared
to using external snapshots.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2017-02-15 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 15:46 [Qemu-devel] Estimation of qcow2 image size converted from raw image Maor Lipchuk
2017-02-13 17:03 ` John Snow
2017-02-13 17:16 ` Daniel P. Berrange
2017-02-13 18:26 ` John Snow
2017-02-15 15:14 ` Stefan Hajnoczi
2017-02-15 15:20 ` Daniel P. Berrange
2017-02-15 15:34 ` Eric Blake
2017-02-15 15:57 ` Nir Soffer
2017-02-15 16:05 ` [Qemu-devel] [Qemu-discuss] " Alberto Garcia
2017-02-15 16:11 ` Daniel P. Berrange [this message]
2017-02-15 16:07 ` [Qemu-devel] " Daniel P. Berrange
2017-02-20 11:12 ` Stefan Hajnoczi
2017-02-15 15:49 ` Nir Soffer
2017-02-20 11:07 ` Stefan Hajnoczi
[not found] ` <CAJ1JNOdzD7DHTHGJEO2YQANDPq0kY-PEh6J1jBkP7hUW0Kvy9w@mail.gmail.com>
[not found] ` <CAMRbyyssi_rspwDJTtWM1Ju5CTZ15z1xBikRDONrS84rx+B8Qg@mail.gmail.com>
2017-02-22 16:15 ` Maor Lipchuk
2017-02-22 22:06 ` Maor Lipchuk
2017-02-28 9:19 ` 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=20170215161117.GK24672@redhat.com \
--to=berrange@redhat.com \
--cc=amureini@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mlipchuk@redhat.com \
--cc=mreitz@redhat.com \
--cc=nsoffer@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=stefanha@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).