From: Stefan Hajnoczi <stefanha@gmail.com>
To: inbox@expertcomputerrepair.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OEM Windows in Qemu
Date: Tue, 20 Dec 2011 09:49:52 +0000 [thread overview]
Message-ID: <20111220094952.GA10603@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20111220000941.dea4083a6cdf20c79465b33709bb47d9.287b6d6c86.wbe@email09.secureserver.net>
On Tue, Dec 20, 2011 at 12:09:41AM -0700, inbox@expertcomputerrepair.com wrote:
> <html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>I've been trying for several days now to get my OEM copy of Windows XP to pre-activate properly in Qemu-kvm. I saw the instructions for patching the seabios here:</div><div><a href="http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg03080.html">http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg03080.html</a><br></div><div><br></div><div>That seems to have worked as expected. When I boot, it shows the newly compiled BIOS, but Windows fails to detect the SLIC codes which I copied from my working Dell system as per the instructions. My research so far has turned up the existence of multiple versions of SLP/SLIC which I think may account for this.</div><div><br></div><div>Can anyone confirm what version of SLP the patch posted to this list is effective at emulating? Is there an easy way to modify the patch to support a different version of SLP?</div><div><br></div><div>I've installed several low level BIOS scanning tools in the VM to troubleshoot and gather information. None of the tools I've used (OEMSCAN, Oembios) show a valid SLP 1.0 OEM data in the BIOS/RAM. But another tool (ReadWrite) shows a valid Dell SLP 2.0 signature. This leads me to believe that either I didn't copy the right SLIC information from my Dell PC or the patch is set up to create SLP 2.0 and not 1.0.</div><div><br></div><div>Any advice or help would be appreciated.</div><div><br></div><div>Brian<br></div><div><br></div><div><br></div></span></body></html>
Please send plain text emails, not HTML to the qemu-devel mailing list.
Your email client or webmail should have an option to choose between
text-only, HTML-only, and text-and-HTML. Either text-only or
text-and-HTML is fine.
Thanks,
Stefan
next prev parent reply other threads:[~2011-12-20 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 7:09 [Qemu-devel] OEM Windows in Qemu inbox
2011-12-20 9:49 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-20 18:23 inbox
2011-12-21 7:53 ` Michael Tokarev
2011-12-22 4:44 inbox
2011-12-22 6:36 ` Michael Tokarev
2011-12-23 6:11 inbox
2011-12-23 6:21 ` ronnie sahlberg
2011-12-23 8:43 ` Jernej Simončič
2011-12-24 6:09 inbox
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=20111220094952.GA10603@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=inbox@expertcomputerrepair.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).