From: Nigel Horne <njh@bandsman.co.uk>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Minix 3.1.2a report
Date: Thu, 26 Apr 2007 13:56:23 +0100 [thread overview]
Message-ID: <4630A177.6080407@bandsman.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
Minix 3.1.2a installs and runs with no difficulty with CVS qemu.
However when I enable kqemu kqemu-1.3.0pre11, Minix hangs on startup
after printing its memory map.
See http://www.minixtips.com/2006/06/running-minix-under-qemu.html for
easy to follow instructions on the installation.
-Nigel
[-- Attachment #2: njh.vcf --]
[-- Type: text/x-vcard, Size: 181 bytes --]
begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
email;internet:njh@bandsman.co.uk
tel;fax:+44 870 705 9334
note:Skype: nigelhorne
x-mozilla-html:FALSE
version:2.1
end:vcard
next reply other threads:[~2007-04-26 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 12:56 Nigel Horne [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-26 12:59 [Qemu-devel] Minix 3.1.2a report Nigel Horne
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=4630A177.6080407@bandsman.co.uk \
--to=njh@bandsman.co.uk \
--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).