From: "Mike Nordell" <tamlin@algonet.se>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Windows 2000 installed without a problem
Date: Fri, 16 Apr 2004 09:56:21 +0200 [thread overview]
Message-ID: <000901c42388$509ff080$0401a8c0@putte2k> (raw)
Using "almost" CVS QEMU on Win32, installing NT5sp4 from a CD image, with
"only" 64 MB of memory given to the guest, but disabling both NE2k and SB16
by means of setting nb_nics=0 before the "nb_nics1 = nb_nics;" at the end of
pc_init() in pc.c, and disabling the calls to AUD_init() and SB16_init(),
I've managed to install NT5sp4 (a "slipstreamed" to sp4 image) without too
much problems.
What I believe is worth noting is that I haven't seen a single gfx "glitch".
DTC and failed to install, and some COM component failed to register, but
that might be due to lack of a NIC (combined with another missing piece in
the emulation, that MS' GUID generation uses in absence of a NIC), but
besides that everything else seemingly worked like a charm.
I therefore can with some certainty say that either the SB16 or the NE2k
code (with the patch from Renzo applied) is a source of bugs - it probably
overwrites memory it doesn't own. As the SB16 code has already read memory
it didn't own, that'd be my first suspect.
Could someone else that's been experiencing spurious guest-crashes, or
installation failures, try to do the same - disable NE2k, OSS and SB16 as I
outlined, and report failure or success? Both Windows and GNU/Linux hosts
would probably be preferred.
/Mike
next reply other threads:[~2004-04-16 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 7:56 Mike Nordell [this message]
2004-04-16 8:33 ` [Qemu-devel] Windows 2000 installed without a problem Jean-Michel POURE
2004-04-16 8:37 ` Jean-Michel POURE
2004-04-16 9:03 ` Mike Nordell
2004-04-16 9:22 ` Jean-Michel POURE
2004-04-16 11:34 ` [Qemu-devel] Windows 2000 installed without a problem (more information) Jean-Michel POURE
2004-04-17 6:59 ` Jean-Michel POURE
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='000901c42388$509ff080$0401a8c0@putte2k' \
--to=tamlin@algonet.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.