qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Martin <jmartin@notamusica.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu floppy emulation problems - partially solved
Date: Tue, 17 Aug 2004 22:40:17 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.56.0408172228020.1927@hatatitla.NotaMusica.com> (raw)

Hi,

a little while ago we had some discussion about floppy emulation not
working in qemu once an OS has been installed. Our assumption was that
floppy access worked through int13 bios emulation but not really down at
the hardware level.

Today I noticed in Win98 that Windows would only offer to format a floppy
at 180kB. I then booted Win98 with a floppy inserted at boot time and
noticed two things:
- rather than two 'removable disk drives' Win98 now only reports one
  3 1/2" floppy drive (correctly)
- I can actually access that floppy and other floppies I insert later
  (no disk change problem as with CDs)

Observations on other OSes:
- Win95 reports a VFAT error and pretty much dies
- OS/2 can access the floppy that was inserted originally, as soon as I
  try to access any other floppy, qemu dies with a segmentation fault.

Tested on Debian/GNU Linux with a two week old qemu/CVS.

So I guess our initial assumption was at least partially incorrect, the
problem is not (primarily) the fdc hardware emulation in general but the
part OSes need to detect the kind of floppy drive installed. Apparently,
if no virtual floppy is inserted, the detection fails. I haven't actually
looked at the code yet - I imagine it to be quite easy to fix though.

Any hints how to find out why/where qemu segfaults under OS/2? How can I
get a core dump out of qemu? So far, my attempts to debug qemu using gdb
have failed miserably. :(

Thanks
	Johannes

             reply	other threads:[~2004-08-17 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 20:40 Johannes Martin [this message]
2004-08-17 20:47 ` [Qemu-devel] Qemu floppy emulation problems - partially solved Johannes Martin
2004-08-18 16:23   ` malc

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=Pine.LNX.4.56.0408172228020.1927@hatatitla.NotaMusica.com \
    --to=jmartin@notamusica.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).