From: Thomas Huth <thuth@redhat.com>
To: Shubham Kumar <kumar.shubham@research.iiit.ac.in>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: Re: [Qemu-devel] regarding bug name : -hda FAT:. limited to 504MBytes
Date: Tue, 14 Feb 2017 23:24:49 +0100 [thread overview]
Message-ID: <6066bf52-d3d9-07d2-1e0f-118b8c19f3f4@redhat.com> (raw)
In-Reply-To: <1202180823.778907.1487108292243.JavaMail.zimbra@research.iiit.ac.in>
Hi,
On 14.02.2017 22:38, Shubham Kumar wrote:
> Since the problem seems like the used FAT-16 file system ,
> Will it solve the problem if I change the code of vvfat.c for FAT-32 file system to increase acceptable file size ?
As far as I know, FAT16 can already support up to 4GB file systems, so
that limitation to 504 MB must be something different.
It's maybe best if you put the qemu-block mailing list on CC:, to get
the attention of the block/disk expert, too. Maybe there's someone
around who knows the vvfat code and its limitations and can give a good
answer here...
Thomas
next prev parent reply other threads:[~2017-02-14 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:38 [Qemu-devel] regarding bug name : -hda FAT:. limited to 504MBytes Shubham Kumar
2017-02-14 22:24 ` Thomas Huth [this message]
2017-02-15 10:10 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
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=6066bf52-d3d9-07d2-1e0f-118b8c19f3f4@redhat.com \
--to=thuth@redhat.com \
--cc=kumar.shubham@research.iiit.ac.in \
--cc=qemu-block@nongnu.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).