qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@qumranet.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [RESEND PATCH v3 0/5] Add UUID support.
Date: Mon, 23 Jun 2008 11:52:13 +0300	[thread overview]
Message-ID: <20080623085213.GA3028@minantech.com> (raw)
In-Reply-To: <20080618060713.GD32664@minantech.com>

Fabrice,

On Wed, Jun 18, 2008 at 09:07:13AM +0300, Gleb Natapov wrote:
> On Wed, Jun 18, 2008 at 12:04:50AM +0200, Fabrice Bellard wrote:
> > Gleb Natapov wrote:
> > > There was no additional comments last time I sent this patch series and
> > > it was not yet committed to the SVN. Resend it for review/inclusion.
> > > 
> > >  This is updated version of the patch series. The patch #5 checks libuuid
> > > availability and uses it for UUID generation if present, but it is
> > > optional so if people think that libvirt is a better place for UUID generation
> > > just don't apply the last patch.
> > 
> > I don't like this vmport "backdoor" and I would like to disable it by
> > default, so I consider it is not the solution to pass the UUID
> > information to the BIOS.
> Do you have other interface in mind for host/guest communication?
> VMware uses the I/O port backdoor interface. Microsoft Virtual PC
> uses "Invalid Opcode" mechanism as a backdoor.
> We need this interface for other things too. For instance there are OEM
> Windows versions that require specific vendor's ACPI table to be present
> for installation. I have a patch that pass additional ACPI tables to BIOS
> using backdoor interface since it's not practical to compile different
> BIOSes for different Windows OEM versions.
> 
> > 
> > BTW, what is the use of this UUID ?
> > 
> It is used for system management to tell two identical computers apart.
> Something like MAC but more stable. In Windows WMI can be used to obtain
> UUID and we have vendors that use VB scripts to configure machines
> differently based on their UUIDs.
> 
Can you share your thoughts on this topic? As Anthony said in one of his
mails that this is a very common feature request for management tools.

Thanks,

--
			Gleb.

  parent reply	other threads:[~2008-06-23  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080616130135.24174.93474.stgit@gleb-debian.qumranet.com.qumranet.com>
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 1/5] Add OUT support to vmport Gleb Natapov
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 2/5] Add -uuid command line option Gleb Natapov
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 3/5] Add "info uuid" command to monitor Gleb Natapov
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 4/5] Add support for UUID query to vmport interface Gleb Natapov
2008-06-16 13:02 ` [Qemu-devel] [RESEND PATCH v3 5/5] Use libuuid if available Gleb Natapov
2008-06-17 22:04 ` [Qemu-devel] [RESEND PATCH v3 0/5] Add UUID support Fabrice Bellard
2008-06-18  6:07   ` Gleb Natapov
2008-06-18 12:13     ` Jamie Lokier
2008-06-23  8:52     ` Gleb Natapov [this message]
2008-10-15 12:46 ` Wing D Lizard
2008-10-30 13:14 ` [Qemu-devel] many messages per hour from Gleb Natapov Wing D Lizard
2008-06-16 13:20 [Qemu-devel] [RESEND PATCH v3 0/5] Add UUID support Gleb Natapov

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=20080623085213.GA3028@minantech.com \
    --to=gleb@qumranet.com \
    --cc=aliguori@us.ibm.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).