From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin O'Connor <kevin@koconnor.net>
Subject: [Qemu-devel] setting OEM ID in BIOS from qemu?
Date: Thu, 17 Mar 2011 13:43:04 +0300 [thread overview]
Message-ID: <4D81E5B8.7020808@msgid.tls.msk.ru> (raw)
Hello.
What's the possible way(s) to set OEM identification
string in BIOS too, so that it provides ACPI tables
with the given identification?
It is needed to support running OEM version of windows
vista and windows 7 (for example) from /dev/sda without
voiding its activation - this needs a real SLIC table
plus the corresponding string other tables (FACP, FACS,
-- I don't know for sure which other table windows
checks, exactly).
First is already available on the host system in
/sys/firmware/acpi/tables/SLIC, and it's possible
to use this table directly with -acpitable file=...
after my patch for hw/acpi.c which I submitted today
for qemu.
The second component is missing currently, hence
this my question.
Thanks!
/mjt
next reply other threads:[~2011-03-17 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 10:43 Michael Tokarev [this message]
2011-03-20 15:20 ` [Qemu-devel] Re: setting OEM ID in BIOS from qemu? Kevin O'Connor
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=4D81E5B8.7020808@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kevin@koconnor.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).