qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] More qcow2 bugs? - qemu-img convert/commit
Date: Thu, 10 Sep 2009 10:32:51 +0200	[thread overview]
Message-ID: <4AA8B9B3.9040002@redhat.com> (raw)
In-Reply-To: <4AA8B865.8000809@redhat.com>

Am 10.09.2009 10:27, schrieb Kevin Wolf:
> Am 10.09.2009 01:26, schrieb Jamie Lokier:
>> 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?
> 
> No, this definitely looks like a bug. I tend to suspect qemu-img rather
> than qcow2, though. After all, your qcow2 image works when a VM reads it
> and from a qcow2 perspective there should be no difference from reading
> in qemu-img.
> 
> I'll have a look at it.

Actually, first of all, which qemu version are you using?

There is a qemu-iotests test case for qemu-img convert with backing
files and git master passes it for me. However, there was a fix to
qemu-img in July (commit d032044fb97d525ae93fb4c96713a5c467044c17)
concerning conversion with backing files.

Kevin

  reply	other threads:[~2009-09-10  8:34 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 ` [Qemu-devel] " Paolo Bonzini
2009-09-10  8:27 ` [Qemu-devel] " Kevin Wolf
2009-09-10  8:32   ` Kevin Wolf [this message]
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=4AA8B9B3.9040002@redhat.com \
    --to=kwolf@redhat.com \
    --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).