From: Filip Navara <navaraf@reactos.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] X86-64 and APIC
Date: Tue, 27 Sep 2005 13:13:38 +0200 [thread overview]
Message-ID: <43392962.5050001@reactos.com> (raw)
In-Reply-To: <dhb2km$pa1$1@sea.gmane.org>
Emmanuel Charpentier wrote:
>Dear List,
>
>Natalia Portillo noticed that XP_64 refused to install due to lack of
>APICs. Filip Navara proposed an initial patch, and Fabribe Bellard
>proposed :
>
>
>
>>I can include the patch with a specific option to enable it. The
>>option will disapear when the hack will be known to be stable.
>>
>>
>
>Fabrice then commited (in July) three APIC-related patches ; the current
>(0.7.2) documentation does not mention APICs. I was therefore under the
>impression that this was a solved issue.
>
>However, trying to use qemu-system-x86_64 (with kqemu) on an AMD64
>system (running under Ubuntu AMD 64 with a hand-compiled (with
>gcc-3.4.5) kernel) to test XP Pro_64 leads to no installation : the
>system complains that it can see no APIC and cannot continue.
>
>Is there an (undocumented) option to enable APIC emulation in this
>configuration (qemu-system-x86-64 + kqemu running under Linux 2.6.12 64
>bits) ?
>
>Or did I hit an unsupported case ?
>
>
Sigh, people write me private mails about this every month. The problem
with Win64 is not APIC, but ACPI (which is used to detect Local APIC
among other things). I've updated version of my hack and experimental
ACPI implementation from malc_, but even with these patches it's NOT
POSSIBLE to install Win64. With all the local patches in my tree I'm
able to get to the second stage setup, but that's all ... it's way too
slow for some reason (not just normal slowness, but some bug probably).
- Filip
prev parent reply other threads:[~2005-09-27 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 9:15 [Qemu-devel] X86-64 and APIC Emmanuel Charpentier
2005-09-27 11:13 ` Filip Navara [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=43392962.5050001@reactos.com \
--to=navaraf@reactos.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 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).