All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qcow2: Allow qcow2 disk images with size zero
Date: Tue, 27 Oct 2009 18:17:38 +0100	[thread overview]
Message-ID: <4AE72B32.8070102@mail.berlios.de> (raw)
In-Reply-To: <4AE72375.3000003@redhat.com>

Kevin Wolf schrieb:
> Am 27.10.2009 15:11, schrieb Anthony Liguori:
>   
>> Stefan Weil wrote:
>>     
>>> Images with disk size 0 may be used for
>>> VM snapshots, but not to save normal block data.
>>>
>>> It is possible to create such images using
>>> qemu-img, but opening them later fails.
>>>
>>> So even "qemu-img info image.qcow2" is not
>>> possible for an image created with
>>> "qemu-img create -f qcow2 image.qcow2 0".
>>>
>>> This is fixed here.
>>>
>>> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
>>>   
>>>       
>> What do you think Kevin?
>>     
>
> That with malloc instead of qemu_malloc the patch would have been a bit
> smaller. ;-) I think it can make sense to have such images in some cases
> (although a 64k image isn't much worse) and I don't see any obvious
> problem with the patch. Not sure how guests like 0 byte disks, but I
> assume Stefan has tested that.
>
> I'm just wondering how Stefan did create his test image - with current
> qemu-img I can't create such images, so I needed to patch it first. For
> this one I'll send a fix.
>
> Kevin
>   

Hi Kevin,

obviously, I called an old version of qemu-img to create the test image
(from debian's qemu package).

Regards
Stefan

      reply	other threads:[~2009-10-27 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 15:11 [Qemu-devel] [PATCH] qcow2: Allow qcow2 disk images with size zero Stefan Weil
2009-10-27 14:11 ` Anthony Liguori
2009-10-27 16:44   ` Kevin Wolf
2009-10-27 17:17     ` Stefan Weil [this message]

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=4AE72B32.8070102@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=kwolf@redhat.com \
    --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.