All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: inbox@expertcomputerrepair.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OEM Windows in Qemu
Date: Thu, 22 Dec 2011 10:36:37 +0400	[thread overview]
Message-ID: <4EF2CFF5.5030003@msgid.tls.msk.ru> (raw)
In-Reply-To: <20111221214425.dea4083a6cdf20c79465b33709bb47d9.7ec28750ba.wbe@email09.secureserver.net>

On 22.12.2011 08:44, inbox@expertcomputerrepair.com wrote:
[]
>> WinXP requires "SLIC version 1.0", which is reduced to just having a string
>> with the name of your OEM in the bios (one possible place is the SLIC table).
>> More recent version of SLIC (2.1 I think) is needed to activate windows7.
> 
> This is the part that is confusing me.  I've read that SLIC 2.0 is
> backward compatible with SLIC 1.0 so XP should activate just fine with a
> working SLIC 2.0.  And your patch does apparently produce a signed SLIC 2.0 

"My patch" does not produce any SLIC at all.  The instructions mentions
using SLIC from your machine - "my patch" is just a way to _embed_ a given
data into VM, not a way to "produce" anything.  You get in your VM what
you have outside, either in a file or in your own BIOS, depending on where
you took that data from.

> But my OEM copy of XP complains about the BIOS produced with your patch.
>  I can only guess there is some critical piece missing that Windows 7
> doesn't care about.

Well.  It should be both - win7 in my case cared about alot more details
than winXP.  But I must admit that I never actually installed oem version
of winXP, -- I used an installed version to verify what it needs, and
found that I can just mention the right string in the BIOS.  Maybe it
is not sufficient for actual "activation" procedure, I dunno.

[]
> I'm guessing this may be significant because the DMI data is different
> in the VM.  Looking at a memory dump of the VM ACPI tables I see several
> tables: RSDP, RSDT, FACP, SSDT, APIC, HPET, SLIC, FACS, and DSDT.
> RSDT and SLIC shows what we would expect: "OEM ID= DELL" "OEM Table ID =
> M07" "OEM Revision = 27D80202".  In other words all the exported SLIC
> data.  But the other tables show "OEM ID = BOCHS" "OEM Table ID = BXPC"
> "OEM Revision = 00000001"  Maybe Windows XP reads from the "wrong"
> tables?

Yes, the patch only changes RSDT to match SLIC - this is what win7 verifies,
all other tables does not matter for win7.  And yes, it might be different
for winXP - you may try setting all tables in VM to be of DELL OEM and see
what happens.

> I assume Seabios reads all of that from src/config.h is that right?  I
> could just change that data and recompile, but would I need to change
> anything else also?  Would that create maybe some other problems down
> the road?

neither seabios nor qemu/kvm actually use these OEM strings, so there
should be no problems.

/mjt

  reply	other threads:[~2011-12-22  6:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  4:44 [Qemu-devel] OEM Windows in Qemu inbox
2011-12-22  6:36 ` Michael Tokarev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-24  6:09 inbox
2011-12-23  6:11 inbox
2011-12-23  6:21 ` ronnie sahlberg
2011-12-23  8:43 ` Jernej Simončič
2011-12-20 18:23 inbox
2011-12-21  7:53 ` Michael Tokarev
2011-12-20  7:09 inbox
2011-12-20  9:49 ` Stefan Hajnoczi

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=4EF2CFF5.5030003@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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 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.