9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: joseph.stewart@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] plan9 on qemu problems...
Date: Tue, 28 Dec 2004 16:06:25 -0500	[thread overview]
Message-ID: <b60c49309644ef78950f6387ca12a89f@plan9.bell-labs.com> (raw)
In-Reply-To: <2781f020412281021410a11fd@mail.gmail.com>

I found the Win32 Qemu to be very flakey, sometimes it would work,
sometimes hang as you describe. It was downloaded, not compiled from
scratch. I found some problems by going into the monitor (ctrl-alt-2)
and dumping the instruction stream at the current pc (x/10i $eip)
then using acid on the kernel binary to see where it was looping
(e.g. in the ne2000 driver if you don't have the 'nodummyrr' option).

--jim

On Tue Dec 28 13:22:19 EST 2004, joseph.stewart@gmail.com wrote:
> I'm running plan9 on qemu under win32 (compiled with MINGW).
> 
> I applied the patches suggested in this list several days ago
> (thanks!), and booted from CD and installed into a HD image... all
> seemed fine until trying to reboot into the newly created HD image.
> 
> I then see:
> 
> dev A0 port 1F0 config 0040 capabilities 0300 mwdma 0000 udma 201F
> dev A0 port 170 config 85C0 capabilities 0200 mwdma 0103
> 
> and qemu seems to "go to sleep" (meaning plan9 never starts up, no
> error messages, etc).
> 
> Here's the line I start qemu up with:
> 
> qemu -L bios -hda p9hd.img
> 
> Anyone else having problems like this?
> 
> What other debug info might I provide that would help fix this?
> 
> Thanks!
> 
> -joe
> 
> -- 
> Person who say it cannot be done should not interrupt person doing it.
>  -- Old Scottish Proverb


      reply	other threads:[~2004-12-28 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 18:21 Joseph Stewart
2004-12-28 21:06 ` jmk [this message]

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=b60c49309644ef78950f6387ca12a89f@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    --cc=joseph.stewart@gmail.com \
    /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).