From: "Filip Navara" <xnavara@volny.cz>
To: Alexander Graf <alex@csgraf.de>
Cc: kvm-devel@lists.sourceforge.net, Ryan Harper <ryanh@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] [PATCH 2 of 3] Optionally link against libuuid if present
Date: Sun, 20 Jan 2008 18:01:10 +0100 [thread overview]
Message-ID: <5b31733c0801200901k279a1f70g70835f45c2e26e07@mail.gmail.com> (raw)
In-Reply-To: <EB2C2C51-0654-4872-98EC-F8EB4497CCAA@csgraf.de>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Jan 20, 2008 5:53 PM, Alexander Graf <alex@csgraf.de> wrote:
>
> On Jan 20, 2008, at 5:37 PM, Filip Navara wrote:
>
> The specific VMware backdoor call isn't implemented, but the framework is
> there and it wouldn't be hard to add support for it. The BIOS can fallback
> to some "reasonable" value if the backdoor isn't available.
>
>
> + memset(bios_uuid, 0, 16);
>
> This value? Why not put something more "reasonable" in there? Does a uuid
> have to meet specific criteria (checksums)? If not, why not simply put
> something like "QEMU" in here? If I remember correctly OSX needs a value in
> the uuid or it fails to boot, so it might be a good idea to give it
> something better than an empty string.
>
Yes, this value. All zeroes means that UUID is not present in the system.
The value has to follow the criteria of SMBIOS specification, section
3.3.2.1, namely it has to be formatted like this:
DWORD time_low;
WORD time_mid;
WORD time_high_and_version;
BYTE clock_seq_hi_and_reserved;
BYTE clock_seq_low;
BYTE node_number[6];
I doubt any driver really checks the value, except maybe for the all-0xFF or
all-0x00 case.
- Filip
[-- Attachment #2: Type: text/html, Size: 1650 bytes --]
next prev parent reply other threads:[~2008-01-20 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 20:08 [Qemu-devel] [PATCH 0 of 3] Add SMBIOS/DMI table generation to PC machine Ryan Harper
2007-12-11 20:08 ` [Qemu-devel] [PATCH 1 of 3] export SMBIOS/DMI tables to PC machines Ryan Harper
2007-12-11 20:08 ` [Qemu-devel] [PATCH 2 of 3] Optionally link against libuuid if present Ryan Harper
2007-12-11 21:19 ` Filip Navara
2007-12-12 22:51 ` Fabrice Bellard
2008-01-03 19:55 ` Ryan Harper
2008-01-20 13:17 ` Filip Navara
2008-01-20 14:25 ` Paul Brook
2008-01-20 15:26 ` Filip Navara
2008-01-20 16:20 ` [kvm-devel] " Alexander Graf
2008-01-20 16:37 ` Filip Navara
2008-01-20 16:53 ` Alexander Graf
2008-01-20 17:01 ` Filip Navara [this message]
2007-12-11 21:21 ` Filip Navara
2007-12-11 20:08 ` [Qemu-devel] [PATCH 3 of 3] Add -uuid command line flag Ryan Harper
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=5b31733c0801200901k279a1f70g70835f45c2e26e07@mail.gmail.com \
--to=xnavara@volny.cz \
--cc=alex@csgraf.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
/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).