From: Paul Brook <paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
To: qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Qemu-devel] Fixing ACPI for Vista -- Source code for bios.bin vs. bochs CVS?
Date: Mon, 30 Apr 2007 20:11:44 +0100 [thread overview]
Message-ID: <200704302011.45291.paul@codesourcery.com> (raw)
In-Reply-To: <8FFF7E42E93CC646B632AB40643802A80282EDB7-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Monday 30 April 2007, Nakajima, Jun wrote:
> We found a way to get 32-bit Vista up on KVM by fixing bios.bin. And I
> think it should be helpful to qemu as well. However, I'm not sure if the
> binary file has been created simply by applying bios.diff to the latest
> bochs CVS tree (actually I doubt it).
What makes you think this won't work? Have you tried it?
Paul
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-30 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 19:04 Fixing ACPI for Vista -- Source code for bios.bin vs. bochs CVS? Nakajima, Jun
[not found] ` <8FFF7E42E93CC646B632AB40643802A80282EDB7-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-04-30 19:11 ` Paul Brook [this message]
[not found] ` <200704302011.45291.paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
2007-04-30 19:42 ` [Qemu-devel] " Anthony Liguori
2007-04-30 22:40 ` Nakajima, Jun
2007-05-01 6:42 ` Avi Kivity
2007-05-01 8:52 ` Gilad Ben-Yossef
2007-05-01 22:09 ` Fixing ACPI for Vista -- Source code for bios.bin vs.bochs CVS? consul
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=200704302011.45291.paul@codesourcery.com \
--to=paul-qd8j1lwmmjjtcj0u4l0sbw@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@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