From: Chris Lalancette <clalance@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Gleb Natapov <gleb@qumranet.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option
Date: Tue, 29 Jul 2008 10:42:24 +0200 [thread overview]
Message-ID: <488ED7F0.5050205@redhat.com> (raw)
In-Reply-To: <20080729081525.GI32498@redhat.com>
Daniel P. Berrange wrote:
> I'd really welcome addition of SMBIOS support too - for x86 the UUID
> in the SMBIOS tables, is the most effective way for a guest admin to
> find their machine identify in a format that can be correlated with
> the host machine by external admin tools. Xen has code for doing SMBIOS
> tables that could be useful to anyone wanting to work on this. Though it
> won't be a straight port since they integrate it with the HVM loader
> firmware, the general data table setup code ought to be reusable, only
> leaving the BIOS integration part.
Again, just to be clear; SMBIOS support is already there today in Bochs BIOS
(you can see this by doing "dmidecode" inside a guest). The only real thing
this patchset was changing was plumbing it through to get the UUID from the Qemu
device model through the VMware back door. Since there seems to be aversion to
the VMware back door, however, the only real question is how we pass UUID
information from the Qemu device model through to the Boch BIOS, so it can place
the UUID in the SMBIOS tables that it is already building. Suggestions so far
have been:
1) Patch the UUID directly into the Bochs BIOS when the Qemu process is loading
it. This is pretty straightforward, but not very extensible.
2) Find or come up with a "standard" backdoor mechanism. I would think this
would be quite similar to the VMware one, but wouldn't be subject to VMware's
whims on it.
Chris Lalancette
next prev parent reply other threads:[~2008-07-29 8:43 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
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 [this message]
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=488ED7F0.5050205@redhat.com \
--to=clalance@redhat.com \
--cc=berrange@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).