From: Magnus Damm <magnus.damm@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] amd64 progress
Date: Fri, 4 Feb 2005 20:37:21 +0100 [thread overview]
Message-ID: <aec7e5c305020411373f416e17@mail.gmail.com> (raw)
In-Reply-To: <4203C69B.4020402@volny.cz>
On Fri, 04 Feb 2005 20:01:47 +0100, Filip Navara <xnavara@volny.cz> wrote:
> I've tried installing the WinXP 64-bit preview under QEMU/x64 on Win32.
> At first I had to add a little hack - hardcoded ACPI table - to enable
> the setup loader to recognize the local APIC. After this the setup
> starts loading the kernel and device drivers, everything works well
> until it tries to jump to the loaded kernel. It crashes fairly quicky
> and ends-up in endless exception loop, because the in-memory kernel
> image is corrupted. The setup loader itself decompressed the image from
> CAB/LZX file stored on a CD-ROM so it's pretty hard to find where's the
> error and I've had no success at debugging it yet. ;-(
>
> (See an example of the image corruption below.)
>
> I would appreciate any suggestions on how to debug it/where the problem
> can be.
A long shot: I recently sent a patch to this list that fixed
installation of win98 from cdrom, the bug was that register DL was
modified during bios calls. The bug only occured when booting from
cdrom. So if you boot from cdrom and use an old bios version I
encourage you to upgrade rombios.c to rev 1.128 and see if that helps.
/ magnus
next prev parent reply other threads:[~2005-02-04 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 22:12 [Qemu-devel] amd64 progress Anand Kumria
2005-02-04 19:01 ` Filip Navara
2005-02-04 19:37 ` Magnus Damm [this message]
2005-02-04 20:12 ` Filip Navara
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 15:41 Matthew Daniel
2005-02-09 16:51 ` Filip Navara
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=aec7e5c305020411373f416e17@mail.gmail.com \
--to=magnus.damm@gmail.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 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.