From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Success!
Date: Tue, 13 Mar 2007 15:22:31 +0200 [thread overview]
Message-ID: <45F6A597.7020304@qumranet.com> (raw)
In-Reply-To: <45F69C98.1020209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity wrote:
> Avi Kivity wrote:
>>
>>> We will have to figure out what the problem in the BIOS is w.r.t.
>>> 4423 before this will work with the code in /trunk, however.
>>>
>>
>> I'll take a look.
>>
>
> I went through a Windows XP install cycle; it worked but no acpi. I
> don't know what fixed this; maybe it was the non-pae fix.
>
> Anyway I've reverted r4423; let's pretend it never happened.
>
Actually that reverted the bios to qemu-0.8.2. Silly me. Anyway I
hacked around it and now Linux boots with acpi and ide dma. I'll try
Windows too.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-03-13 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 23:46 Success! Gregory Haskins
[not found] ` <45F5AE1B.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-03-13 9:46 ` Success! Avi Kivity
[not found] ` <45F67312.4090105-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-13 12:44 ` Success! Avi Kivity
[not found] ` <45F69C98.1020209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-13 13:22 ` Avi Kivity [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=45F6A597.7020304@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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