All of lore.kernel.org
 help / color / mirror / Atom feed
From: Filip Navara <xnavara@volny.cz>
To: matthew.daniel@oversightsystems.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] amd64 progress
Date: Wed, 09 Feb 2005 17:51:57 +0100	[thread overview]
Message-ID: <420A3FAD.5090605@volny.cz> (raw)
In-Reply-To: <1107963684.4949.43.camel@dhcp113.oversighttech.com>

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Matthew Daniel 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.
>>    
>>
>Is this change committed to CVS or if not may I ask to see it?
>
It's a hack and as such it can't really be commited to CVS. The code is 
attached.

>Bochs has
>the same problem as my CVS qemu and (at least according to their mailing
>list) they are stumped about how to get around this issue.
>  
>
I've made a similar hack to Bochs while testing... I do not intend to 
share the source since it's even uglyier than the QEMU one, sorry. With 
the hack Win64 under Bochs get about to the same point as in QEMU. There 
seem to be some problems with segment limit checks in the x86-64 mode, 
but I haven't tried to investigate it further...

Regards,
Filip

[-- Attachment #2: qemu-acpi-hack.zip  --]
[-- Type: application/x-zip-compressed, Size: 1119 bytes --]

  reply	other threads:[~2005-02-09 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 15:41 [Qemu-devel] amd64 progress Matthew Daniel
2005-02-09 16:51 ` Filip Navara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-03 22:12 Anand Kumria
2005-02-04 19:01 ` Filip Navara
2005-02-04 19:37   ` Magnus Damm
2005-02-04 20:12     ` 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=420A3FAD.5090605@volny.cz \
    --to=xnavara@volny.cz \
    --cc=matthew.daniel@oversightsystems.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.