qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
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: Tue, 29 Jul 2008 09:15:25 +0100	[thread overview]
Message-ID: <20080729081525.GI32498@redhat.com> (raw)
In-Reply-To: <488DD98D.5010907@codemonkey.ws>

On Mon, Jul 28, 2008 at 09:37:01AM -0500, Anthony Liguori wrote:
> Gleb Natapov wrote:
> >Hi Chris,
> >
> >On Mon, Jul 28, 2008 at 03:25:06PM +0200, Chris Lalancette wrote:
> >  
> >>All,
> >>     Attached is a three part patch series to implement a "-uuid" 
> >>     command-line
> >>option to qemu.  The original work for this was all done by Gleb Natapov; 
> >>since
> >>there hadn't seemed to be any activity on this since June, I picked up his
> >>patches and ran with them (original posting:
> >>http://www.archivum.info/qemu-devel@nongnu.org/2008-06/msg00167.html).  
> >>These
> >>patches are basically the same as his, just cleaned up according to 
> >>Anthony
> >>Liguori's feedback.
> >>    
> >Actually there was activity on this. I addressed Anthony's feedback and
> >reposted the patch series (I think even twice). Here is the last one:
> >http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00448.html
> >http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00442.html
> >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/msg00445.html
> >http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00446.html
> >
> >Fabrice said that he doesn't like vmware backdoor interface though
> >(http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00487.html)
> >I asked what interface he wants to use for qemu/guest communication, but
> >he never replied to this :(
> >  
> 
> The backdoor interface is deprecated (from a VMware perspective) and is 
> pretty terrible.  I'll go through and do a more thorough review of the 
> patches Chris posted but one thing I already know I'd like to see the 
> UUID plumbed through the SMBIOS tables for x86.  That's a requirement in 
> my mind for adding a -uuid option.  I see no harm in also supporting the 
> backdoor interface but the primary way to expose a UUID should be SMBIOS.

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.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  parent reply	other threads:[~2008-07-29  8:42 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 [this message]
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=20080729081525.GI32498@redhat.com \
    --to=berrange@redhat.com \
    --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).