From: Paolo Bonzini <bonzini@gnu.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: More qcow2 bugs? - qemu-img convert/commit
Date: Thu, 10 Sep 2009 01:42:27 +0200 [thread overview]
Message-ID: <4AA83D63.1070101@gnu.org> (raw)
In-Reply-To: <20090909232654.GA20719@shareable.org>
> 37% is large enough to be a clue: Does it simply expand the qcow2 file
> without reading the backing file at all? A quick strace shows that
> indeed, it does *open* the backing file and it does read the backing
> file's header, but after that it doesn't read it at all.
>
> Did I miss something obvious which means this is ok?
>
> Should the output of "qemu-img convert" be identical to the backing
> file after "qemu-img commit", assuming they are the same format?
I would have thought so.
Paolo
next prev parent reply other threads:[~2009-09-09 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 23:26 [Qemu-devel] More qcow2 bugs? - qemu-img convert/commit Jamie Lokier
2009-09-09 23:42 ` Paolo Bonzini [this message]
2009-09-10 8:27 ` Kevin Wolf
2009-09-10 8:32 ` Kevin Wolf
2009-09-10 9:44 ` Jamie Lokier
2009-09-10 9:46 ` Kevin Wolf
2009-09-10 12:27 ` Jamie Lokier
2009-09-11 19:28 ` Jamie Lokier
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=4AA83D63.1070101@gnu.org \
--to=bonzini@gnu.org \
--cc=jamie@shareable.org \
--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 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).