qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vmdk: Fix creating big description file
Date: Tue, 3 Dec 2013 09:42:23 +0100	[thread overview]
Message-ID: <20131203084223.GA12840@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <529D41FA.2060705@redhat.com>

On Tue, Dec 03, 2013 at 10:29:14AM +0800, Fam Zheng wrote:
> On 2013年12月02日 21:26, Stefan Hajnoczi wrote:
> >On Mon, Dec 02, 2013 at 11:01:20AM +0800, Fam Zheng wrote:
> >>The buffer for description file was 4096 which only covers a few
> >>hundred of extents. This changes the buffer to dynamic allocated with
> >>g_strdup_printf in order to support bigger cases.
> >>
> >>Signed-off-by: Fam Zheng <famz@redhat.com>
> >>---
> >>  block/vmdk.c               |   65 +-
> >>  tests/qemu-iotests/059     |    5 +
> >>  tests/qemu-iotests/059.out | 2012 ++++++++++++++++++++++++++++++++++++++++++++
> >>  3 files changed, 2058 insertions(+), 24 deletions(-)
> >
> >Does VMware have a hard limit?  For example, does it open the 1000 GB
> >twoGbMaxExtentFlat file from your test case?
> >
> 
> Yes it does. The limit is far above this, there is a statement in
> VMDK spec: "Maximum VMDK file size is 2TB." It opens this file from
> the test case, however I can't generate such a twoGbMaxExtentFlat
> from Workstation, because it will be automatically forced to
> monolithicFlat (if the size is above certain threshold).

Okay, good.  Thanks for explaining.

Stefan

      reply	other threads:[~2013-12-03  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02  3:01 [Qemu-devel] [PATCH] vmdk: Fix creating big description file Fam Zheng
2013-12-02 13:26 ` Stefan Hajnoczi
2013-12-03  2:29   ` Fam Zheng
2013-12-03  8:42     ` Stefan Hajnoczi [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=20131203084223.GA12840@stefanha-thinkpad.muc.redhat.com \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).