From: Gleb Natapov <gleb@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Lalancette <clalance@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/3]: vmware backdoor interface fix
Date: Tue, 29 Jul 2008 08:31:39 +0300 [thread overview]
Message-ID: <20080729053139.GL3196@minantech.com> (raw)
In-Reply-To: <488E2348.7000004@codemonkey.ws>
On Mon, Jul 28, 2008 at 02:51:36PM -0500, Anthony Liguori wrote:
> But if we're going to support a -uuid option, then I don't want it to
> only work with the backdoor interface. It should be plumbed through to
> the SMBIOS tables because this is what users are going to expect.
>
This is exactly what's happening now. BOCHS BIOS adds UUID to SMBIOS
table. You can see UUID that you provide on command line by running
"dmidecode | grep UUID" in a Linux guest. If you worry that UUID
backdoor is accessible from a guest then we can make it one shot
i.e disable it after first query.
> However, we should not be using the backdoor interface as a
> communications mechanism between QEMU and the Bochs BIOS.
>
OK. What about applying these patches (I can resend them if needed):
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00443.html
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00444.html
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00446.html
They add -uuid command line option, but don't plumb UUID into the BIOS.
We will figure out later how to pass it there.
--
Gleb.
prev parent reply other threads:[~2008-07-29 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 13:25 [Qemu-devel] [PATCH 1/3]: vmware backdoor interface fix Chris Lalancette
2008-07-28 18:58 ` [Qemu-devel] " Anthony Liguori
2008-07-28 19:18 ` Gleb Natapov
2008-07-28 19:51 ` Anthony Liguori
2008-07-29 5:31 ` Gleb Natapov [this message]
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=20080729053139.GL3196@minantech.com \
--to=gleb@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=clalance@redhat.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).