From: "Yann Le Doaré" <yledoare@linuxconsole.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: qemu disk on vfat
Date: Tue, 09 May 2006 23:41:01 +0000 [thread overview]
Message-ID: <1147218062.9211.2.camel@localhost> (raw)
In-Reply-To: <pan.2006.05.08.21.12.33.879704@codemonkey.ws>
You are right ! :
sh-2.05b# qemu-img create /mnt/partitions/windows0/qmeu-disk 4M
Formating '/mnt/partitions/windows0/qmeu-disk', fmt=raw, size=4096 kB
sh-2.05b# ls -al /mnt/partitions/windows0/qmeu-disk
-rwxr-xr-x 1 root root 0 2006-05-09
23:37 /mnt/partitions/windows0/qmeu-disk
sh-2.05b# qemu-img create /mnt/partitions/windows0/qmeu-disk 40M
Formating '/mnt/partitions/windows0/qmeu-disk', fmt=raw, size=40960 kB
sh-2.05b# ls -al /mnt/partitions/windows0/qmeu-disk
-rwxr-xr-x 1 root root 0 2006-05-09
23:38 /mnt/partitions/windows0
Le lundi 08 mai 2006 à 16:12 -0500, Anthony Liguori a écrit :
> On Sun, 07 May 2006 08:13:01 +0000, Yann Le Doaré wrote:
>
> > Hi,
> >
> > It seems like qemu 0.8.0 does not accept image file from a vfat partition.
> > Is it a bug ?
> >
> > Greetings.
> >
> > Yann Le Doaré.
> >
> >
> > strace :
> >
> > open("/mnt/partitions/windows0/qmeu-disk", O_RDONLY|O_LARGEFILE) = 7
> > read(7, "", 1024) = 0 close(7)
> > = 0 open("/mnt/partitions/windows0/qmeu-disk",
> > O_RDONLY|O_LARGEFILE) = 7 _llseek(7, 128, [128], SEEK_SET) = 0
> > read(7, "", 4) = 0 close(7)
> > = 0 write(2, "qemu: could not open hard disk i"..., 74qemu: could
> > not open hard disk image '/mnt/partitions/windows0/qmeu-disk' ) = 74
> > exit_group(1) = ?
>
> It's pretty clear that what's happening is that qemu opening the file and
> the filesystem is claiming it's an empty file.
>
> So, I recommend you do the following:
>
> First:
>
> du -sh /mnt/partitions/windows0/qmeu-disk
> ls -al /mnt/partitions/windows0/qmeu-disk
>
> And make sure both report a non-zero result. If either reports 0 as the
> size, then you screwed up copying the file to your vfat partition.
>
> Second:
>
> In vl.h, change:
>
> #ifndef O_LARGEFILE
> #define O_LARGEFILE 0
> #endif
>
> To:
>
> #ifdef O_LARGEFILE
> #undef O_LARGEFILE
> #endif
> #define O_LARGEFILE 0
>
> And if that fixes your problem, then vfat is broken when open()'d with
> O_LARGEFILE. If that's the case, you should report it as a vfat bug.
>
> Regards,
>
> Anthony Liguori
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2006-05-08 21:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 10:04 [Qemu-devel] qemu disk on vfat Yann Le Doaré
2006-05-07 8:44 ` André Braga
2006-05-08 10:41 ` Yann Le Doaré
2006-05-07 15:50 ` [Qemu-devel] " Alex
2006-05-07 11:00 ` [Qemu-devel] " NyOS
2006-05-07 13:47 ` Jernej Simončič
2006-05-08 19:44 ` Yann Le Doaré
2006-05-08 14:57 ` Jan Marten Simons
2006-05-09 21:05 ` Yann Le Doaré
2006-05-07 11:21 ` Johannes Schindelin
2006-05-08 21:12 ` [Qemu-devel] " Anthony Liguori
2006-05-09 23:41 ` Yann Le Doaré [this message]
2006-05-08 22:05 ` Michael McConnell
2006-05-08 22:48 ` Jim C. Brown
2006-05-08 23:10 ` Jim C. Brown
2006-05-08 23:50 ` Jim C. Brown
2006-05-09 1:36 ` Anthony Liguori
2006-05-09 2:11 ` Paul Brook
2006-05-16 17:21 ` Jim C. Brown
2006-05-08 22:23 ` Ian C. Blenke
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=1147218062.9211.2.camel@localhost \
--to=yledoare@linuxconsole.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).