All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Bug 826363 <826363@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 826363] Re: qemu-img convert does not work with vdi files
Date: Sat, 20 Aug 2011 12:15:44 +0200	[thread overview]
Message-ID: <4E4F8950.8060002@mail.berlios.de> (raw)
In-Reply-To: <4E4F756C.3060907@mail.berlios.de>

Am 20.08.2011 10:50, schrieb Stefan Weil:
> Am 17.08.2011 18:44, schrieb Stefan Hajnoczi:
>> On Wed, Aug 17, 2011 at 5:29 PM, Stefan Hajnoczi <stefanha@gmail.com> 
>> wrote:
>>> On Tue, Aug 16, 2011 at 7:07 PM, Steve Si 
>>> <826363@bugs.launchpad.net> wrote:
>>>> I got binaries from http://homepage3.nifty.com/takeda-toshiya/
>>>>
>>>> tested under Win 7 64-bit as User=Administrator
>>>>
>>>> qemu10.6 - works  makes      16/08/2011  18:43     3,096,481,792 
>>>> test.raw
>>>> qemu11.1 - works  makes      16/08/2011  18:43     3,096,481,792 
>>>> test.raw
>>>> qemu12.1 - crashes !
>>>> qemu12.2 - crashes !
>>>> qemu12.5 - error while writing
>>>
>>> I think this crash->error transition is explained by:
>>>
>>> commit 8cef921d18025b4ce4e749eed391308033fee232
>>> Author: TeLeMan <geleman@gmail.com>
>>> Date:   Mon Feb 8 16:20:00 2010 +0800
>>>
>>>    qemu-img: use the heap instead of the huge stack array for win32
>>>
>>> But we still don't know why you are getting the write error.  It would
>>> be fairly easy to find that out by building QEMU from source and
>>> adding fprintf() where the write fails - print out the error code and
>>> sector number.
>
> The current code only supports images (any format) with less than
> 4 GiB (maybe even less than 2 GiB).
>
> This limitation is caused by the usage of function ftruncate to create
> the destination file. ftruncate takes a long (32 bit) parameter.

I did not notice that ftruncate is mapped to qemu_ftruncate64, so my
analysis was not correct. The implementation of qemu_ftruncate64
was buggy. It's fixed now, and working binaries are available from
http://qemu.weilnetz.de/w32/2011-08-20/.

  parent reply	other threads:[~2011-08-20 10:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 16:32 [Qemu-devel] [Bug 826363] [NEW] qemu-img convert does not work with vdi files Steve Si
2011-08-14 21:25 ` [Qemu-devel] [Bug 826363] " Steve Si
2011-08-15 21:12 ` [Qemu-devel] [Bug 826363] [NEW] " Stefan Hajnoczi
2011-08-15 22:59 ` [Qemu-devel] [Bug 826363] " Steve Si
2011-08-16 13:10   ` Stefan Hajnoczi
2011-08-16 18:07 ` Steve Si
2011-08-17 16:29   ` Stefan Hajnoczi
2011-08-17 16:44     ` Stefan Hajnoczi
2011-08-20  8:50       ` Stefan Weil
2011-08-20  8:57         ` Michael Tokarev
2011-08-20 10:10         ` [Qemu-devel] [PATCH] w32: Fix qemu_ftruncate64 Stefan Weil
2011-08-20 12:01           ` Stefan Weil
2011-08-22 16:32           ` Anthony Liguori
2011-08-20 10:15         ` Stefan Weil [this message]
2011-08-17 18:46 ` [Qemu-devel] [Bug 826363] Re: qemu-img convert does not work with vdi files Steve Si
2011-08-17 19:05 ` Steve Si
2011-08-19  4:14   ` Stefan Hajnoczi
2011-08-19 19:06 ` Steve Si
2011-08-20 12:21 ` Stefan Weil
2011-08-20 17:13 ` Steve Si
2011-08-27 16:23 ` Steve Si
2011-08-27 19:42 ` Stefan Weil
2012-02-15  6:17 ` Stefan Weil
2013-02-03  9:28 ` Aaron Bouzek
2013-02-03  9:38 ` Aaron Bouzek

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=4E4F8950.8060002@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=826363@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.