qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "consul" <consul@collegeclub.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Size of virtual FAT disk limit?
Date: Thu, 5 Jul 2007 14:42:12 -0700	[thread overview]
Message-ID: <f6jojm$g8l$1@sea.gmane.org> (raw)

Hi,

I'm running into a problem with virtual FAT disks. If the source directory 
contents size
significantly exceeds 494673920 (0x1D7C2000) bytes, I get an error:
Assertion failed: index < array->next, file c:/qemu/block-vvfat.c, line 97

If the sise only slightly exceeds (even by one byte) this limit, I get the 
different error:
Directory does not fit in FAT16

This seems strange, as this limit is not even close to 2GB limit imposed by 
FAT16.

I tried quite recent qemu CVS version from 6/28/07 on Windows XP host.
qemu -L . -hda c:\qemu-img\test.q2 -hdb fat:\test2 -fda 
c:\qemu-img\boot.ima -boot a
Will try it on Linux later.

Any comments on the error?

Alex. 

             reply	other threads:[~2007-07-05 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 21:42 consul [this message]
2007-07-10 23:00 ` [Qemu-devel] Re: Size of virtual FAT disk limit? consul

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='f6jojm$g8l$1@sea.gmane.org' \
    --to=consul@collegeclub.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 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).