From: Tom Marble <tmarble@info9.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Drive success FAT16, NTFS, failure with FAT32
Date: Thu, 03 Feb 2005 16:37:52 -0600 [thread overview]
Message-ID: <4202A7C0.7080105@info9.net> (raw)
Fabrice:
I have been able to configure qemu (from CVS yesterday)
to use the following drives:
In each case I used bximage (interactively) to create
the raw image files (which I left to the Windows installers
to partition and format). I probably could/should
have used qemu-img instead.
FAT16
503 MB
Type: 0x0e W95 FAT16 LBA
Installed Windows 98 successfully
NTFS
2000 MB
Type: 0x07 HPFS/NTFS
Installed Windows XP successfully
I was unsuccessful, however, in creating FAT32 filesystems,
even those < 512 MB.
Using fdisk to set /dev/hda1 to type 0x0b WIN95 FAT32
and creating the filesystem with mkdosfs -F 32
did create a disk that was recognized by the Windows 98
installer. Windows complained about bad clusters.
Using type 0x0c WIN95 FAT32 (LBA) and formatting the
disk made the Windows 98 installer happy.
However on the first reboot after installation
the BIOS complained of a Disk I/O Error.
Once it actually got farther and said Booting... but then
just hung.
I made various attempts at adding -hdachs arguments
but none succeeded in making the FAT32 disk recognized.
I have not looked at the code that examines the MBR
or trys to mount the partition based on the
type, but I suspect that's the next place to look.
I have to say I am *very* impressed with qemu!
In my debugging I tried to see if bochs would work
with FAT32 -- and it didn't (same BIOS as qemu) -- but it ran much,
much slower (probably the 4x slower people have mentioned).
One can imagine using the bochs BIOS to debug
ACPI and PXE related issues as well.
Merci pour cet excellent logiciel!
--Tom
reply other threads:[~2005-02-03 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4202A7C0.7080105@info9.net \
--to=tmarble@info9.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 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).