qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gilad Ben-Yossef <gilad@codefidence.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] Fixing ACPI for Vista -- Source code for bios.bin vs.	bochs CVS?
Date: Tue, 01 May 2007 11:52:24 +0300	[thread overview]
Message-ID: <4636FFC8.6020103@codefidence.com> (raw)
In-Reply-To: <8FFF7E42E93CC646B632AB40643802A80282EDB7@scsmsx412.amr.corp.intel.com>

Howdie,

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). Can somebody provide a recipe for
> creating bios.bin from the bochs tree so that we can make a patch?
> 

While we wait patiently for the patch, would you mind putting the patched bios.bin somewhere accessible (or sending it 
to me in private email and I'll put it somewhere accessible)?

There's a bunch of geeks here that would really like to best test this... :-)

Thanks!
Gilad

-- 
Gilad Ben-Yossef <gilad@codefidence.com>
Codefidence. A name you can trust(tm)
http://www.codefidence.com
Phone: +972.3.7515563 ext. 201  | Cellular: +972.52.8260388
SIP: gilad@pbx.codefidence.com	| Fax: +972.3.7515503

  parent reply	other threads:[~2007-05-01  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 19:04 [Qemu-devel] Fixing ACPI for Vista -- Source code for bios.bin vs. bochs CVS? Nakajima, Jun
2007-04-30 19:11 ` Paul Brook
2007-04-30 19:42   ` Anthony Liguori
2007-04-30 22:40   ` Nakajima, Jun
2007-05-01  6:42   ` [kvm-devel] " Avi Kivity
2007-05-01  8:52 ` Gilad Ben-Yossef [this message]
2007-05-01 22:09 ` [Qemu-devel] Re: 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=4636FFC8.6020103@codefidence.com \
    --to=gilad@codefidence.com \
    --cc=jun.nakajima@intel.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --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).