qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu problem (you might be my last resort)
Date: Mon, 21 Mar 2005 15:01:12 -0500	[thread overview]
Message-ID: <20050321200112.GA32293@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <423F065B.8050709@compuserve.de>

On Mon, Mar 21, 2005 at 06:37:31PM +0100, Robin Pfeifer wrote:
> >>Not quite. The first disk I tried was a very old DOS 6.0 I still have 
> >>lying around (I haven't got that many boot floppies anymore), and it 
> >>didn't quite finish booting - but I thought, maybe the disk is broken. 
> >>But I have also tried a Linux-based floppy which I have used as a boot 
> >>disk previously, and downloaded bootE and tried that, too - I'm finding 
> >>the kernel simply stops booting after a while. It does boot normally 
> >>during a real boot process.
> >
> >Ok, so where does it stop booting? At what point does it freeze?
> 
> The BootE floppy stops while the display says 'Loading' with a row of 
> dots. But when the emulation window is started, it always displays 'qemu 
> stopped' for a short moment, after which the 'stopped' disappears and 
> the BIOS messages appear in the window. This short moment is what the 
> other attempts do not get over. The floppy emulation passes that.
> 

I assume Linux boot floppy stops at the same point?

> /dev/hdb doesn't work, I have no second IDE harddisk - I've got one IDE 
> and one SCSI harddisk. /dev/hda results in the 'qemu stopped' error, hdb 
> of course in a 'could not open hard disk image'.
> 
> I have downloaded the Freedos image and started it with
> 
> qemu -hda /path/to/freedos.img -snapshot
> 
> Same error: qemu stopped.
> 

I can't reproduce this error. Using latest CVS, 'qemu -m 350' works perfectly
fine for me. In fact it works fine for qemu 0.5.5 as well.
Only difference is that I use kerenl 2.4.26 and I have the rtc set to 100hz
instead of 1024hz. I also have never installed or used kqemu.

Can you run gdb on it and figure out where in the code it freezes?

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2005-03-21 20:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20  7:01 [Qemu-devel] qemu problem (you might be my last resort) Robin Pfeifer
2005-03-20 16:06 ` Jim C. Brown
2005-03-20 20:49   ` Robin Pfeifer
2005-03-21  0:57     ` Jim C. Brown
2005-03-21 17:37       ` Robin Pfeifer
2005-03-21 20:01         ` Jim C. Brown [this message]
2005-03-21 21:02           ` Robin Pfeifer
2005-03-25 21:38           ` [Qemu-devel] qemu crashes at boot start Robin Pfeifer
2005-03-25 22:04             ` Antony T Curtis
2005-03-25 22:30               ` Robin Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
2005-03-18  9:10 [Qemu-devel] qemu problem (you might be my last resort) Robin Pfeifer
2005-03-18 15:45 ` Jim C. Brown
2005-03-18 16:44   ` Stefan Kisdaroczi
2005-03-09 20:06 Robin Pfeifer
2005-03-11 17:20 ` Jim C. Brown

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=20050321200112.GA32293@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --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).