From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Gleb Natapov <gleb@qumranet.com>, Chris Lalancette <clalance@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option
Date: Mon, 28 Jul 2008 17:28:28 +0100 [thread overview]
Message-ID: <20080728162828.GA14004@shareable.org> (raw)
In-Reply-To: <488DF11D.7090100@codemonkey.ws>
Anthony Liguori wrote:
> >CMOS has enough memory for UUID, but UUID is not the only thing that
> >needs to be passed to BIOS, so eventually we can run out of space there.
> >
>
> I'm inclined to think that on a real machine, the UUID is stored in the
> CMOS.
I'd imagine on a real machine the UUID cannot be changed, so it can't
be stored in the CMOS. It's probably in the BIOS somewhere.
I quick Google suggests at least some systems store it in the SMBIOS
information, which is part of the BIOS EEPROM. It also suggested that
some Dell laptops store it in the keyboard controller!
The logical equivalent would be to directly write the UUID (and other)
information into the Bochs BIOS when loading it into the emulator.
> >For example we have a requirement to pass additional ACPI tables that
> >user may specify on command line.
>
> What's the use-case? I don't think this is a very good idea.
For testing guest ACPI implementations or changing their behaviour? :-)
> You can not arbitrarily extend the backdoor interface. It's an
> interface defined and controlled by VMware. If you extend it, you risk
> breaking other OSes that are assuming that interface has a different
> meaning.
I agree, better to define a sensible interface if extensions are
desired.
Probably at least one other VM has defined such a thing, it would be
good to copy if there is one and it's extensible.
-- Jamie
next prev parent reply other threads:[~2008-07-28 16:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 13:25 [Qemu-devel] [PATCH 0/3]: Add UUID command-line option Chris Lalancette
2008-07-28 14:15 ` [Qemu-devel] " Gleb Natapov
2008-07-28 14:37 ` Anthony Liguori
2008-07-28 14:41 ` Chris Lalancette
2008-07-28 15:02 ` Anthony Liguori
2008-07-28 15:09 ` Chris Lalancette
2008-07-28 15:12 ` Anthony Liguori
2008-07-28 15:42 ` Chris Lalancette
2008-07-28 16:02 ` Gleb Natapov
2008-07-28 16:17 ` Anthony Liguori
2008-07-28 16:27 ` Gleb Natapov
2008-07-28 17:41 ` Blue Swirl
2008-07-28 16:28 ` Jamie Lokier [this message]
2008-07-28 19:02 ` Anthony Liguori
2008-07-28 20:00 ` Jamie Lokier
2008-07-28 20:25 ` Anthony Liguori
2008-07-28 20:40 ` Paul Brook
2008-07-28 20:55 ` Anthony Liguori
2008-07-29 6:31 ` Gleb Natapov
2008-07-28 15:48 ` Jamie Lokier
2008-07-31 19:45 ` [Qemu-devel] " Sebastian Herbszt
2008-07-28 15:49 ` [Qemu-devel] " Jamie Lokier
2008-07-28 16:06 ` Anthony Liguori
2008-07-28 15:35 ` Gleb Natapov
2008-07-29 19:22 ` Anthony Liguori
2008-07-29 19:50 ` Gleb Natapov
2008-07-30 17:32 ` Blue Swirl
2008-08-05 14:33 ` Gleb Natapov
2008-08-06 2:35 ` Anthony Liguori
2008-08-06 16:26 ` Blue Swirl
2008-08-06 16:33 ` Anthony Liguori
2008-08-06 22:07 ` [Qemu-devel] " Sebastian Herbszt
2008-08-06 22:11 ` [Qemu-devel] " Anthony Liguori
2008-07-29 8:15 ` Daniel P. Berrange
2008-07-29 8:42 ` Chris Lalancette
2008-07-28 15:51 ` Jamie Lokier
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=20080728162828.GA14004@shareable.org \
--to=jamie@shareable.org \
--cc=clalance@redhat.com \
--cc=gleb@qumranet.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).